I would like some suggestions for a decent rom. I am looking for pure vanilla android and the possibility of using the new Google Assistant and having the Pixel Launcher.
I am also looking for a tweaked bluetooth setting. The one in stock sucks in my car.
Thanks
cwis said:
I would like some suggestions for a decent rom. I am looking for pure vanilla android and the possibility of using the new Google Assistant and having the Pixel Launcher.
I am also looking for a tweaked bluetooth setting. The one in stock sucks in my car.
Thanks
Click to expand...
Click to collapse
Any US996 rom will run without issue on H910. I think the closest to a vanilla android rom you're going to find right now would be one of the CM-built roms, like LineageOS or AOKP. You will lose second-screen functionality with these roms, though. Not sure if by 'tweaked bluetooth setting' you mean signaling because of audio dropping out, or equalizer-type changes. If you have audio drops, try a different kernel. Konverged and Restock both took care of mine. For sound settings, those roms may have Viper4Android or something similar in them already.
I'm running WETA + Restock kernel on my H910. No static, no bluetooth issues, way too much audio control.
No issues installing that Restock kernel? Do you flash the ROM then the kernel and SuperSU in that order?
The roms should be pre-rooted, so no need to flash supersu. But yes, flash the rom, then the kernel in TWRP immediately after each other.
I haven't had any issues with Restock at all.
ugoff said:
Any US996 rom will run without issue on H910. I think the closest to a vanilla android rom you're going to find right now would be one of the CM-built roms, like LineageOS or AOKP. You will lose second-screen functionality with these roms, though. Not sure if by 'tweaked bluetooth setting' you mean signaling because of audio dropping out, or equalizer-type changes. If you have audio drops, try a different kernel. Konverged and Restock both took care of mine. For sound settings, those roms may have Viper4Android or something similar in them already.
I'm running WETA + Restock kernel on my H910. No static, no bluetooth issues, way too much audio control.
Click to expand...
Click to collapse
Bluetooth sputter and dropping out. It's also a pain in the ass to pair in my car, but not a pia with my other bt devices. Weird.
cwis said:
Bluetooth sputter and dropping out. It's also a pain in the ass to pair in my car, but not a pia with my other bt devices. Weird.
Click to expand...
Click to collapse
I've also found this happens in my car, but it's not due to the bluetooth stack on the phone. I believe it has to do with the power output of the transmitter or maybe the antenna. The mount I use is directly above and sticks out past the front of the face of my stereo. With the phone upright or in landscape to the left, it drops signal. When in landscape with the top of the phone to the right, I have no drops. When it's in this position, more of the phone is closer to the stereo, which sounds like an interference issue. It also doesn't drop when the phone is upside down in the mount, but it's covering more than half the front of my stereo in that position. I also don't have issues if the phone is in my lap on on the passenger seat, hence my suspicion about interference.
Is there any option yet to be rooted while still being able to wifi call on any rom or kernel?
Just need to tether really, without losing wifi calling ability.
Wait, what..?
ugoff said:
Any US996 rom will run without issue on H910. I think the closest to a vanilla...[/unquote]
Please disabuse me of my ignorance, but does this mean that my h910 (rooted) can flash Nethunter (the 996 version is supported, has kernel, etc)?
Click to expand...
Click to collapse
hubrisnxs said:
ugoff said:
Any US996 rom will run without issue on H910. I think the closest to a vanilla...[/unquote]
Please disabuse me of my ignorance, but does this mean that my h910 (rooted) can flash Nethunter (the 996 version is supported, has kernel, etc)?
Click to expand...
Click to collapse
Yes. Nethunter was one of the first roms I flashed on my H910.
Click to expand...
Click to collapse
.
ajent said:
Is there any option yet to be rooted while still being able to wifi call on any rom or kernel?
Just need to tether really, without losing wifi calling ability.
Click to expand...
Click to collapse
If I understand you correctly, I should flash lineage, then nethunter over it, then flash the gapp, su, and xposed zips?
Or, are you saying i should, from my att phoe, flash the 997 nethunter build from offsec, then build my own chroot, kernel, annnnnd I;ll stop there
Related
Been lurking around this forum for a few months now, but only decided to post now, lol.
So we all know that the bluetooth drivers for ASOP and Sense ROMs are from different. There are quite a few threads on this forums and others regarding the issues that people have with the Sense BT driver, which range from low quality audio output to inability to pair with certain devices.
The problem that I have with all the Sense ROMs (from the older MikFroyo to the newer Synergy Sense ROMs and MikG) is that the BT connection between my phone and my car (an 09 BMW 3-series) continuously drop and reconnect whenever the phone attempts to transfer the contact list to the car. But in all the ASOP roms I have tried (CM7, Deck, SalvageZen), the phone and car paired perfectly and all the contacts transferred to the car without any issue.
I attempted to fix this issue myself. So I simply switched the bluetooth.apk file in system/app folder of the downloaded zip file for the Sense ROM with the one from CM7. And I also replaced bluetoothd file in system/bin and all the .conf files in system/etc/bluetooth with CM7 counterparts. This actually worked with the older Froyo based Sense ROMs, namely MikFroyo, which I used for the longest time.
However, when I tried to same thing with newer GB-based Sense ROMs. This method no longer work. The phone either drop connection and reconnect repeatedly like before (which was seen with Synergy, Kingdom, Virus's ROM). Or the bluetooth can't be turned on at all as in MikG ROMs (which I suspect is because the conflict between the apk and odex files).
Anyway, I am just wondering anyone can take a look into this problem and see if there is a way to replace the Sense driver with the ASOP one. I think this would solve the majority of BT that people are experiencing with all the sense roms.
Need some help here, bump!
As I understand it, you can't just replace the BT stack in a Sense ROM with the stack from an AOSP ROM because they're too integrated into the frameworks.
Also note: A-O-S-P = Android Open Source Project. ASOP wrote fables. (I know, I know, don't bother pointing out the misspelling.)
Well I figured that the BT stack is integrated into the frameworks. And I didn't really expect that simply replacing some files from AOSP stack can work in froyo based sense ROM. But it did work nonetheless.
So I figured it probably won't be too difficult to replace the BT stack in the GB based sense ROM. Maybe someone with experience can change framework a little to make this work.
shameless bump
guess no one cares enough...
No, it's not that nobody cares. It's that it wouldn't be that easy. I know you said you just dropped a few files in and boom, AOSP BT stack on FroYo. I'm not saying your wrong or making it up...but several people have tried swapping the AOSP stack in and weren't successful. It might have still worked, but it wasn't the AOSP stack (i.e., A2DP still sounded like crap). I really don't think it's as simple as just swapping a couple files, though that doesn't mean it's impossible either.
Cloud9Blue said:
guess no one cares enough...
Click to expand...
Click to collapse
Or maybe people who want AOSP Bluetooth are just using an AOSP ROM.
If you get this to work definitely let me know. I've been looking for the same thing.
swapping the kernel + .so modules may do the trick
arent the bluetooth drivers in the kernel? or as separate .so modules? how about someone trying swapping the kernel in addition to the modules.
The bluetooth stack is in the kernel. You can not use an AOSP kernel on a Sense ROM so that will not help you.
You may want to check out the Freedom kernel. This is a Sense Gingerbread kernel by lithid. He is in the process of swapping out the bluetooth stack for the AOSP stack. The kernel itself is pretty stable but the BT stack work is still very early in development. He wants to be able to support bluetooth controllers (like the PS3 and Wii) but this may also solve the problems that you are having.
The test version with the AOSP stack is Test v0.9.5 and the discussion starts in the middle of page 289 of the thread.
hootnath said:
arent the bluetooth drivers in the kernel? or as separate .so modules? how about someone trying swapping the kernel in addition to the modules.
Click to expand...
Click to collapse
Thanks for the suggestion but this doesn't work. I tried exchanging all of the related bluetooth files with the ones in Deck's rom.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
m20120 said:
The bluetooth stack is in the kernel. You can not use an AOSP kernel on a Sense ROM so that will not help you.
You may want to check out the Freedom kernel. This is a Sense Gingerbread kernel by lithid. He is in the process of swapping out the bluetooth stack for the AOSP stack. The kernel itself is pretty stable but the BT stack work is still very early in development. He wants to be able to support bluetooth controllers (like the PS3 and Wii) but this may also solve the problems that you are having.
The test version with the AOSP stack is Test v0.9.5 and the discussion starts in the middle of page 289 of the thread.
Click to expand...
Click to collapse
Hopefully this works. Thanks for the heads up!
Unfortunately the kernel did not solve me issue. I tried to combine the kernel with the zip mijjah74 created but this didn't work either. I think lithid-cm is on to something with the kernel, but I think modding the kernel isn't enough. I think the AOSP Bluetooth files have to be incorporated some way.
jpflaw00 said:
Unfortunately the kernel did not solve me issue. I tried to combine the kernel with the zip mijjah74 created but this didn't work either. I think lithid-cm is on to something with the kernel, but I think modding the kernel isn't enough. I think the AOSP Bluetooth files have to be incorporated some way.
Click to expand...
Click to collapse
Basically, yes. Lithid-cm is going to try to integrate the ASOP bluetooth stack into the next version of his kernel. The current 0.9 version does not include any kind of support for the ASOP stack and you are advised not to attempt the swap yourself. It requires code changes to the kernel and is not as simple as swapping the .so module.
MultiDev said:
Basically, yes. Lithid-cm is going to try to integrate the ASOP bluetooth stack into the next version of his kernel. The current 0.9 version does not include any kind of support for the ASOP stack and you are advised not to attempt the swap yourself. It requires code changes to the kernel and is not as simple as swapping the .so module.
Click to expand...
Click to collapse
Sounds good. I know that swapping files randomly wouldn't work but I decided to try it anyways. Thanks for the reply.
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Sent from my PC36100 using xda premium
lithid-cm said:
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Click to expand...
Click to collapse
I wish you the best of luck, but one thing at a time buddy
getting a ps3 controller to work is also going to require enabling usb-host in the kernel too(right? or do we need a dongle to do that like other phones?) as well as finding a male mini usb to male micro usb cable (do they make those?), as a ps3 controller has to be paired over USB before working wirelessly.
Honestly I don't understand what HTC did to muck up BT so badly. If everything works in plain ol' AOSP android then what the hell did they do to cripple it?
lithid-cm said:
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Thanks for taking on the challenge. Hopefully you can get this working!!
OK,
So I'm trying to get some help regarding this issue. I will continue to try different ROM's and what not to see if it can be resolved. I'm simply at a loss to where the issue lies though, however as of today, every custom ROM has been giving me trouble. My plan for today is to flash a stock ROM via Odin and then if that works go for Imperium, however I'm hoping with your help I may be able to solve it on something like CM12 or what not because I prefer the flexibility of a proper custom ROM.
OK, so the issue I have:
I have a car head unit which has bluetooth built-in. Music plays fine through Bluetooth, no jitters or issues. However, when I try and call someone and I'm listening to the radio or something non-Bluetooth, the phone does not send the signal (?) to the head unit to switch to Bluetooth. This means the call will be made via the dialer app and while the audio IS being routed through the bluetooth channel, the head unit does not know about it because it hasn't received the signal to switch to Bluetooth. I can switch it manually to Bluetooth and make and receive calls, but this isn't convenient at all and probably quite dangerous when I'm driving a car. The same applies when receiving a call.
Here's the thing, if I go into Bluetooth, select CAR KIT and go configuration, if I disable Media Audio, then it works fine! The phone correctly sends the signal to switch to Bluetooth and the head unit does so. The call goes through and it all works fine. This is repeatable.
Therefore, the issue I'm having lies in the fact both Media and Phone Audio are enabled at the same time. Has anyone else had this issue and does anyone have a suggestion to fix it?
Before someone suggests "just disable media audio". My answer is no, this isn't convenient at all. I use Bluetooth media quite a lot, and simply disabling and re-enabling it everytime simply isn't an option.
So far, I've had this issue on:
CM12.1 Optimized
CM12.1 Nightly
Mokee ROM
DirtyUnicorns
CM12 Nightly
I'm yet to try a stock Lollipop ROM. I know for a fact however, that stock KitKat DOES work.
I really could do with some help here, so any suggestions would be awesome.
all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved
DSA said:
all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved
Click to expand...
Click to collapse
The Bluetooth itself is fine. Audio quality is fine. Call quality is fine. It just seems like a tiny little thing that's causing all these issues for me, because if it could trigger my car head unit to switch, I wouldn't even dream of stock. Also the camera seems fine to be fair?
I'm not keen on going back to stock.... at all, so I'm thinking Imperium. It's a shame though because apart from this BT issue, CM12 is fantastic on this device. Takes a 2 year old phone and makes it feel like a brand new phone.
I really hope someone can fix that Bluetooth bug in CM12.1. I may even look myself, it must be something pretty small from a coding perspective because as I said, the functionality is clearly there as evidenced by the fact it works with Media audio turned off.
Regardless, thanks anyway
Changing the modem did not solve my problem.
When did you try the Optimized and the nightlies? There have been a lot of fixes lately regarding bluetooth.
Maybe the other way arround
Here is the thread on spotify support:
https://community.spotify.com/t5/An...-679-beta/m-p/4415303/highlight/false#M128660
After I have real problems with five lineageOS devices here with a spotify family account I tried nearly everything to find the problem. With the Android Device and LineageOS on it I could not find the speakers who should habe connected the Spotify (Connect).
After I tried a fresh stock device I noticed that all speakers are avaible under the same account and with any other LineageOS Device I missed these speakers.
Frank
After doubeling the MAC, no VoLTE, WLan call problems with the audio mixer and several other things this is a killing point for me now with LineageOS. Thank you to all developers in basic!
Same problem with an Xperia M2 Lineage OS 14.1 (https://forum.xda-developers.com/xperia-m2/general/unofficial-lineageos-14-1-t3747579)
Louis
Same problem here but i'm not sure if LOS is the reason why Spotify Connect isn't working correctly.
https://community.spotify.com/t5/An...ng-since-v8-4-42-679-beta/m-p/4486524#M132741
I was just able to test everything with a non-rooted device without LOS: Everything is working just fine
That means Spotify won't like rooted phones.
Unfortunately it seems so
Same issue here. Neither latest or older APKs work.
Lineage 14.1, potter
I still love the ROM too much to leave it, but this is an unfortunate development. I hope Spotify isn't reading the build number of Android phones and determining it to be custom; they might lose a large amount of customers that way.
Jrhotrod said:
Same issue here. Neither latest or older APKs work.
Lineage 14.1, potter
I still love the ROM too much to leave it, but this is an unfortunate development. I hope Spotify isn't reading the build number of Android phones and determining it to be custom; they might lose a large amount of customers that way.
Click to expand...
Click to collapse
Is your phone rooted or not? I think it's related to root and not ROM. And i'm sure Spotify can identify each used device.
geronimoge said:
Is your phone rooted or not? I think it's related to root and not ROM. And i'm sure Spotify can identify each used device.
Click to expand...
Click to collapse
Rooted, but passing Safety net. So it shouldn't matter.
Jrhotrod said:
Rooted, but passing Safety net. So it shouldn't matter.
Click to expand...
Click to collapse
Okay, i don't know about that. The problem still exists for me.
In case anyone uses Adaway, here some further informations:
https://github.com/AdAway/AdAway/issues/1009
I today tried to use spotify connect with a device with OmniRom and have the same problem.
Even using spotify version 8.4.38.621 and Magisk 16.4. with Magisk Hide.
So i would say it's somehow related to root.
Can anyone agree or disagree?
If it's really not related to LOS perhaps the thread owner can move this thread to get the right attention?
Here having this same problem with two Xiaomis with LOS 15.1. Any idea how to fix this?
juukeli said:
Here having this same problem with two Xiaomis with LOS 15.1. Any idea how to fix this?
Click to expand...
Click to collapse
Are you using AdAway, AFWall or other stuff which changes settings that could be relevant?
I'm having troubles using my G6 (lineage 14.1 installed) with my car Bluetooth. Music plays fine but phonecalls are a nightmare, I can hear the person I call but he/she can barely hear me because he/she does hear a lot of noise (just like when you blow on the microphone). I'm going to test it with my friends cars as well; mine is a Mazda and is working perfectly with a old LG G3, few One+, few Samsung Galaxy and a Lumia.
Anyone else having the same issue? Any tips?
Thanks
How did it work with the stock O/S?
Cnstb said:
I'm having troubles using my G6 (lineage 14.1 installed) with my car Bluetooth. Music plays fine but phonecalls are a nightmare, I can hear the person I call but he/she can barely hear me because he/she does hear a lot of noise (just like when you blow on the microphone). I'm going to test it with my friends cars as well; mine is a Mazda and is working perfectly with a old LG G3, few One+, few Samsung Galaxy and a Lumia.
Anyone else having the same issue? Any tips?
Thanks
Click to expand...
Click to collapse
I.m pretty sure all the custom roms for H870 have calling over BT broken so far.
This is the only reason why I'm still on stock Oreo rom. I need my BT calling working.
Apparenttly it's a driver issue as US version of G6 doesn't have this problem on custom roms.
patruns said:
How did it work with the stock O/S?
Click to expand...
Click to collapse
Good question; honestly, I don't know. I just bought the phone last week, turned it on just to see it worked, did shut it down and installed Lineage.
-Arturo- said:
I.m pretty sure all the custom roms for H870 have calling over BT broken so far.
This is the only reason why I'm still on stock Oreo rom. I need my BT calling working.
Apparenttly it's a driver issue as US version of G6 doesn't have this problem on custom roms.
Click to expand...
Click to collapse
Damn, is there anything we/I can do to try help lineage developers fix this thing?
Cnstb said:
Good question; honestly, I don't know. I just bought the phone last week, turned it on just to see it worked, did shut it down and installed Lineage.
Damn, is there anything we/I can do to try help lineage developers fix this thing?
Click to expand...
Click to collapse
Head over to Aquarius rom thread as there are a few guys claiming the BT calling issues have been fixed.
https://forum.xda-developers.com/lg...ios-8-1-0-live-support-theming-t3808498/page3
Any working solution? I tried viper4android but It did not solve the issue.
I noticed many bluetooth options on rom menu settings, working somewhere gives good response?
Seems like car bluetooth phonecalls with my H870 running lineage 14.1 20181221 nightly do work on a brand new Kia Rio owned by a friend of mine. I'll give it another try with my cars as well and also few other friends cars and see if bt calls have been finally fixed or it's just the Kia the lucky one
My most recent two mods, includig my current rom, Lineage_KTLE 9, cannot maintain a persistent Bluetooth connection. I've tried all my headset connections on different devices and they work fine, but on this G900T, I get nothing but drop-outs and crashes, which is especially frustrating when I'm on an important call.
I've ever considered going back to stock.
Anyway, can someone point me in the right direction? Or is there a working 'radio' I can install to fix this problem?
HaytamFrh said:
Use stock ROM or install an updated bluetooth driver from the hardware manufacturer of the Bluetooth Chip. Something Like R-R Works fine for me synpax's.
Click to expand...
Click to collapse
Can you help me find "R-R Works" so I can access that driver, please?