Related
DISCLAIMER: It is now 5AM and I've had about 8 hours of sleep over the past 48 hours so I might be imagining things. I'm pretty sure there is a difference in audio quality, but without 2 phones side by side, it's hard to compare
Instructions:
1) Flash any DesireHD ROM, your choice!
2) Flash the attached zip file with CWM (it includes the Inspire 4G kernel)
3) Install the attached PropEditor apk, and run it.
4) Open build.prop using PropEditor and change
Code:
htc.audio.hac.enable=0
to
Code:
htc.audio.hac.enable=1
5) Hit the menu button and save! REBOOT!! win?
Let me know how it goes! I do hope I'm not going crazy
I'll update tomorrow with what exactly I did. Too tired to type it out now, GOODNIGHT.
THE DIFFERENT VERSIONS:
-V2: Better quality than V3, speakerphone microphone does not work
-V3-test: Slightly worse quality than V2, better than no sound fix, speakerphone microphone works 100%
palletguru said:
Went back to audio V2. I can personally attest to the fact that the sound is as good as stock - did a side by side with coworker's non routed inspire.
Click to expand...
Click to collapse
CHANGELOG:
V3-test: Removed extra files, sound quality is around the same (or slightly worse) compared to V2. Speakerphone Mic should work
V2: Removed AIC3254_REG_DualMic_MCLK.csv and AIC3254_REG_DualMic.csv as suggested by BelacNongaw to fix mic
Testing her now, thanks!!
Btw, which DHD Roms have you tested using this fix?
I'll report back after testing it (Core Droid DHD)
r34p3rex said:
DISCLAIMER: It is now 5AM and I've had about 8 hours of sleep over the past 48 hours so I might be imagining things. I'm pretty sure there is a difference in audio quality, but without 2 phones side by side, it's hard to compare
Instructions:
1) Flash any DesireHD ROM, your choice!
2) Flash the attached zip file with CWM (it includes the Inspire 4G kernel)
3) Install the attached PropEditor apk, and run it.
4) Open build.prop using PropEditor and change
Code:
htc.audio.hac.enable=0
to
Code:
htc.audio.hac.enable=1
5) Hit the menu button and save! REBOOT!! win?
Let me know how it goes! I do hope I'm not going crazy
I'll update tomorrow with what exactly I did. Too tired to type it out now, GOODNIGHT.
Click to expand...
Click to collapse
Hey whats up man...I know this might be asking a lot is there a way to a make a video about this? But no rush on it bro.. Cause you have been busy with this stuff
Although still not perfect, its 10x better than before with the telus. Unless I forgot the quality of stock which could be possible. But there is definitely a huge difference, to the point that I'm not going back to telus. Good work! Plus, the stock source kernel is being used which is always the best for stability eventhough telus didn't cause any stability problems.
Inspire (rooted)
Leedroid v2.0.0
Telus kernel
AOSP Lockscreen
Exception to my last post, it actually did fix everything! Audio in media player sounds as it should, ringtones sound perfect, etc. This thing is now perfect! Dhd roms, using stock kernel with perfect audio, themes, root access in less than a week! I love xda!
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
Could unrooted people use that apk to enable hsupa in the build.prop? I'm curious....
Sent from my Inspire 4G using XDA App
The hsupa category is 6. What would should it be at to enable hsupa?
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
No good on other end they can't here anything.
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
davwman said:
The hsupa category is 6. What would should it be at to enable hsupa?
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
Click to expand...
Click to collapse
Well I'd have to compare the stock build.prop to the DHD one that people have installed, but there are these values in the DHD one:
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 10
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 3
Guessing one of those is changed in the stock. Will check later
EDIT: Just pulled the build.prop off my unrooted phone and they look the same... odd
failed to remount system rw
I keep getting an error when trying to save build.prop after editing. "failed to remount system rw". I tried creating a backup and editing that then restoring it but got the same error. Am I missing something simple?...lol...thanks
I've been working on this too. Remove AIC3254_REG_DualMic_MCLK.csv and AIC3254_REG_DualMic.csv from /system/etc/ in the zip and this will work without breaking the mic. Good job.
BelacNongaw said:
I've been working on this too. Remove AIC3254_REG_DualMic_MCLK.csv and AIC3254_REG_DualMic.csv from /system/etc/ in the zip and this will work without breaking the mic. Good job.
Click to expand...
Click to collapse
You guys are great!
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
wildace408 said:
I keep getting an error when trying to save build.prop after editing. "failed to remount system rw". I tried creating a backup and editing that then restoring it but got the same error. Am I missing something simple?...lol...thanks
Click to expand...
Click to collapse
Another way to edit build.prop is
Reboot into recovery
Under mounts and partitions mount system
On the computer:
adb pull /system/build.prop
Edit build.prop
adb push build.prop /system/build.prop
Yay sounds great with my HD2 !!
davwman said:
You guys are great!
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
Click to expand...
Click to collapse
does the sound now work on both ends? can you hear who you are talking to and can they hear you?
If the OP removes the two files from the zip that I mentioned in my post, yes. Until then, you can browse the zip with astro on the phone and delete them yourself before flashing.
so do I need to remove those two files from the zip? Im just about to flash a new rom and this kernel and then edit.
aNdroidnut said:
so do I need to remove those two files from the zip? Im just about to flash a new rom and this kernel and then edit.
Click to expand...
Click to collapse
Yes, or you won't have a working mic.
did i do it wrong?
I'm unable to save, so i save it to sdcard then move the file to /system
I did not remove anything.
I leave myself a voicemail, I can hear myself just fine!
netnerd said:
did i do it wrong?
I'm unable to save, so i save it to sdcard then move the file to /system
I did not remove anything.
I leave myself a voicemail, I can hear myself just fine!
Click to expand...
Click to collapse
Remove the two files as mentioned and follow the steps posted by the OP.
Introduction
Hey guys
Last night I got my new NFC tags and, of course, went ahead and configured one for my car. What it does is irrelevant (turns on Bluetooth and 3G, turns off Wi-Fi when I get into the car, and turns off Bluetooth and GPS when I leave it), but what's important is that I was absolutely sure I could use it when the screen is off or even unlocked.
It was a bit of annoying to turn on the phone and unlock the display to use an NFC tag, when the entire purpose of a tag (in my view) is to let me do stuff without touching the display!
I found a few apks, but all of which were reported to make NFC FC/crash or not work at all. The suggested solution based on the Xposed framework was unavailable due to site problems, so i decided to see how difficult it is to implement one on my own...
What is this mod?
This mod, as you might have guessed already, simply lets you use an NFC tag when the screen is off or locked.
Installation
Very simple indeed:
Download the included Nfc.apk file,
Do a nandroid backup (backuping your current Nfc.apk (located at /system/app/Nfc.apk) to someplace safe should suffice, but a nandroid is still recommended),
Copy the included Nfc.apk to /system/app/Nfc.apk,
Change permissions to 'rw-r--r--' ('chmod g-w', 'chmod 644' or your favorite file explorer),
Reboot.
Changlog
Version 1.0:
First release!
Covering my *** part
I am not responsible for any nuclear wars that may result from downloading and installing this Nfc.apk, nor am I responsible for your device breaking, bricking, rebooting, data loss, etc.
About making this mod (and credits)
It was actually surprisingly easy. Figuring how to decompile the APK into a smali (using APK Multi-Tool), and where to go (Geniusdog254's explanation was simple but excellent) was quite easy, and from there it was the road to success.
Also, looking at the relevant code was very helpful (although Samsung added some extra checks, the original code to delete was still very much there).
I also made sure to delete only NFC-C related code, and not to touch anything else (including NFC-EE and SMX, UICC, CardMode, etc).
Do note I am using a DMB6-based ROM (Phoenix v10), but I compared the decompilation output of DME1 and the entire code is identical, so it should be safe to install on any DMB6-and-newer ROMs.
Also, this should only be used on a deodexed ROM.
Enjoy!
making life easier, a flashable zip.
as always, its never wrong to make backup before flashing
enjoy
thank you OP for providing us this mod.. THANKS~~!!
Freezeil said:
Installation
Very simple indeed:
Download the included Nfc.apk file,
Do a nandroid backup (backuping your current Nfc.apk (located at /system/app/Nfc.apk) to someplace safe should suffice, but a nandroid is still recommended),
Copy the included Nfc.apk to /system/app/Nfc.apk,
Change permissions to 'rw-r--r--' ('chmod g-w', 'chmod 644' or your favorite file explorer),
Reboot.
Enjoy!
Click to expand...
Click to collapse
It doesn't work on stock MC3, am I missing something?
attached stock apk here
xcxa23 said:
making life easier, a flashable zip.
as always, its never wrong to make backup before flashing
enjoy
thank you OP for providing us this mod.. THANKS~~!!
Click to expand...
Click to collapse
Why your script have command to change permission of bootanimation.zip instead of Nfc.apk??
dr.ketan said:
It doesn't work on stock MC3, am I missing something?
attached stock apk here
Click to expand...
Click to collapse
Apologies, I never meant it to run a stock ROMs...
Give me some time to see if I can make it work on stock
No problem, If it is made for deodexed rom only then it would be better if you can edit title/OP
Sent from my GT-N7100 using xda premium
Good idea (didn't even think about it... ), but let me see if I can make it for odexed roms as well beforehand.
It is my first mod ever so bare with me
Sent from my GT-N7100 using Tapatalk 2
Just send me apk with this process
Reodexed your existing rom - deodexed again
Will check it, i have seen sometimes this works.
Sent from my GT-N7100 using xda premium
As you might have known, the APK you sent me doesn't contain the actual code (the dex files).
I downloaded a stock odexed MC3 ROM and saw that the code is pretty much the same (didn't make sure), but it would not be possible to make an MC3-compatible odex file from my ROM (which is ME1).
Also, afaik, the odex file also contain other stuff (like dependencies and such), so I wouldn't try replacing the .odex file without re-odexing the entire ROM. Even after replacing the .odex file, I think matching files in /data also need to be replaced, and I read someplace that doing nasty woodoo like this might cause bootloops...
Is there anyone here who's running MC3 ROMs and willing to re-oxed it to its entirety and try this?
I'm getting ready to give this a try on Beans 17. Will let you know the results and shower you with thanks if it works.
UPDATE: You are officially my hero. Works like a charm.
Just ran it on beans 17 and it also works for me.
I'm curious to know how this will affect battery life.
Thanks for this great mod.
Is there any other chance to wake screen with NFC than tasker since secure settings and simplistic framework won't work with each other?
I tried installing it on my Droid razr maxx HD. No luck though . The NFC option disappears from the system settings.
EDIT: I'm retarded. It's probably because this is only modded for Galaxy Note II.
Just letting everyone this also works for AT&T Galaxy Note II LTE.
Awesome!!!!!!
Sent from my GT-N7105 using xda premium
A bit of shame not working on Akop rom. I liked your idea. Can I post the nfc from Akop if that can help?
Does this work for Verizon note 2?
Has anyone tried this on Galaxy S3 (GT-I9300 international).
Nearly forgot - I'm running OmegaRom 46.1 (4.2.2)
I want it for exactly the same reasons - nfc tag in car to switch on BT, sync with stereo and launch BeyondPod playlist without having to unlock.
This shouldn't work
Though send me framework-res.apk, twframework-res.apk and Nfc.apk (deodexed)
will look to it.
Hi,
what could be for reasons that the modified NFC-Version on my SG Note 2 LTE (German) does not work?
Does anyone have any advice?
regards
Vinz
I quite like the Rogers 4.4.2 kitkat build, other then the carrier name being displayed in the upper left of the status bar. A little searching here indicated user "Ctrl-Freak" had patched his AT&T 4.4 build to remove the carrier name. I contacted him and asked if he could patch the Rogers 4.4.2 build for me. The next day I had a patched SystemUI.apk file to install on my Moto X.
To install this file you will need to be rooted and running the Rogers 4.4.2 build.
I used TWRP to backup the two original files - /system/priv-app/SystemUI.apk and /system/priv-app/SystemUI.odex
I then copied the patched SystemUI.apk over the original and deleted the SystemUI.odex. Just to be safe ensure the permissions on the new SystemUI.apk are 0644.
Reboot and you're good to go.
I believe this only works with the Dalvik runtime.
You can get the patched file here:
http://www.androidfilehost.com/?fid=23329332407569175
You can see Ctrl-Freak's original AT&T mod instructions here:
http://forum.xda-developers.com/showthread.php?t=2548806
100% of the credit for this goes to Ctrl-Freak !!!
edit:
I have created an updated version myself(never hurts to learn how to do this stuff) that has the battery percent meter enabled as well as the text inside the battery switched to a slightly larger font and changed to black.
You can download it here:
http://thesteve.ca/motox/statusbar/patched/SystemUI.apk
Steve-x said:
I quite like the Rogers 4.4.2 kitkat build, other then the carrier name being displayed in the upper left of the status bar. A little searching here indicated user "Ctrl-Freak" had patched his AT&T 4.4 build to remove the carrier name. I contacted him and asked if he could patch the Rogers 4.4.2 build for me. The next day I had a patched SystemUI.apk file to install on my Moto X.
To install this file you will need to be rooted and running the Rogers 4.4.2 build.
I used TWRP to backup the two original files - /system/priv-app/SystemUI.apk and /system/priv-app/SystemUI.odex
I then copied the patched SystemUI.apk over the original and deleted the SystemUI.odex. Just to be safe ensure the permissions on the new SystemUI.apk are 0644.
Reboot and you're good to go.
I believe this only works with the Dalvik runtime.
You can get the patched file here:
http://www.androidfilehost.com/?fid=23329332407569175
You can see Ctrl-Freak's original AT&T mod instructions here:
http://forum.xda-developers.com/showthread.php?t=2548806
100% of the credit for this goes to Ctrl-Freak !!!
Click to expand...
Click to collapse
Since you have TWRP, you have root.
Xposed Installer
HideCarrierMotoX
Works on Rogers 4.4.2
No need to overwrite anything, easily reversible.
Two thumbs up!
koocheese said:
Since you have TWRP, you have root.
Xposed Installer
HideCarrierMotoX
Works on Rogers 4.4.2
No need to overwrite anything, easily reversible.
Two thumbs up!
Click to expand...
Click to collapse
Yup....I found this eventually too. Works great.
But good find Steve-x on an alternative for non xposed users.
Sent from my Moto X cellular telephone...
Using xposed would be easier, but I have seen people report it can cause a little bit of lag. Since I only wanted the one change I think this is a more efficient mod.
I may try it out too.
Sent from my Moto X cellular telephone...
I have created an updated version myself(never hurts to learn how to do this stuff) that has the battery percent meter enabled as well as the text inside the battery switched to a slightly larger font and changed to black.
You can download it here:
http://thesteve.ca/motox/statusbar/patched/SystemUI.apk
.
Highlights:
Android 5 - Lollipop
Integrates the latest Dhollmen Kernel.
Supports NTFS file system.
Supports EXFAT filesystem.
Supports F2FS filesystem.
Available configuration options for Dhollmen Kernel overclock.
Integration of Viper4 Audio FX as an equalizer, amplifier and sound effects manager.
Supports for Joystick and game controllers.
Supports for gestures on the keyboard.
First Installation:
Download the zip file from Rom as tablet model
Download the add-on with pre-settings Viper4 Convolver IRS
Download the add-on with Google applications (Gapps)
Boot the tablet in recovery mode
Make "wipe data / factory reset" at this time
Install the Rom file
Install the Viper4 IRS file
Install The Gapps file
Reboot
Subsequent installations:
Download the updated zip file
Reboot to recovery mode
Do NOT any kind of "wipes"
Install the updated zip file
Reboot
Information:
Frequently asked questions you must read.
Downloads:
Recovery TWRP
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: Your assumes at your SOLE RESPONSIBILITY all results produced by the "software" and/or instructions in this thread.
XDA:DevDB Information
Dhollmen, ROM for the Samsung Galaxy Tab 2
Contributors
tuxafgmur
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Current Beta Version: 5.0.2
Beta Release Date: 2015-02-09
Created 2015-02-03
Last Updated 2015-02-15
.
> Rom's Notes.
Who installs this Rom, accept it "as is".
Contains just the apps and options installed.
What you want to add will have to be obtained from Google-Play or any other sources.
Please, don't report bugs if you are not using the installed Dhollmen Kernel.
In case of questions or comments, you must indicate additional apps, tweaks or installed "optimizations".
if you insert images, do it in a 'hide' tag. This hide your image until an user click to show it.
I assume you has installed a suitable Recovery and know how to perform the required steps.
Keep in mind that Antutu and others related apps give you very similar values, regardless of the Rom used.
In such apps, OC influence on speed, but its goal is to evaluate the hardware, not the Rom.
Don't use any kind of overclock before three consecutive stability test in Antutu.
> Rom take a long time to boot after installing.
It is quite normal because ART is used and applications are self-compiled at first boot time, after installing a new Rom.
> Applications are slow to start after installing.
It is quite normal because ART is used and have self-compiled before first use.
Although it may seem at times, the Rom is not hung, just have to wait.
> Get Root access.
In Settings app, entering development option and select Root access.
If you don't see these items, we activate:
Touch repeatedly on About tablet > build number. From now on, initial setting screen show that option, plus Performance.
> Get Performance access.
If you don't see these items, we activate:
Touch repeatedly on About tablet > build number. From now on, initial setting screen show that option, plus Development option.
> Google Apps (Gapps).
All Gapps packages available are virtually identical.
Only differ, from each other, in the amount of installed applications.
Never two different packages must be installed as likely to cause Google applications FC.
The Dhollmen Gapps, being valid for any Rom, are specifically adapted for installation on it.
> Viper4 - Convolver - IRS.
This application controls the System Sound FX.
It also includes a number of advanced pre-equalizer settings (made by others) that are the IRS whose installation files requested.
Access to Convolver (manager of the IRS) is obtained by selecting the option Expert in Experience Settings.
Using another equalizer (provided by external applications) usually interfere with it.
You can only have one active equalizer in the system, but if you want to use another one, kindly Viper4 can be turned off.
> Restoring backups.
It is very common Titanium Backup (or similar) problems in Rom.
If backup /data partition are made and, after a change of Rom, restored, usually side effects will occur.
In this directory and subdirectories it contains, there are many configuration files and internal databases.
When it comes to a specific application should not be a problem as long as it is not part of the Rom.
When sub-directories containing settings are restored, the likelihood of problems increases exponentially.
For example, all Roms have a Settings application, but the content of his configurations differs between them and is not interchangeable.
Under no circumstances you should restore /system partition apps.
> Brick Bug.
Don't worry about.
No problems here
> Recovery.
In the wave of failures of equipment, widely discussed and until the problem is completely cleared
The user is strongly advised not to use another recovery than Dhollmen TWRP-2.8.0.5 or Andi TWRP-2.8.0.1
First impressions: very smooth ??
Before I had slimlp. Did a full wipe and factory reset and installed it. No problems at all!
First reboot was much quicker than slimlp.
So far didn't find any problem with it.
Great job already Dhollmen.
Grtz,
John
---------- Post added at 09:40 PM ---------- Previous post was at 08:41 PM ----------
First hickup: YouTube video's won't play
BTW: nice bootlogo. Very smooth and subtile
Grtz,
John
Can't install, Error 7
Hi, great work but after trying several themes they are not working
Error Status7
gucio9377 said:
Can't install, Error 7
Click to expand...
Click to collapse
Please, be advised to change recovery for newest. I've used PhilzTouch6.59 and had not any problem with installation of ROM.
hello,
try many times to download but don't succeed
Up and running. Thank you tux!
Sent from my GT-P5110 using Tapatalk
Update: I have no audio. Viper installed properly but no video or touch or notification sounds on 5110, sorry to report.
Sent from my GT-P5110 using Tapatalk
Error code
Negative results, error code #65537. Unable to flash with latest TWRP 2.8.4.0 - P5110 recovery. Reverting back to: Dhollmen SlimROM based KitKat 4.4.4 - 2015/ 01/ 18. As always, thank you anyway!
Very nice!
I've flashed and tested this ROM for P5100.
Flashing was sucsessfully after CM11 without any problem. Tablet becames quicker and smoother.
Some problems:
1. Phone part does not work. But with SMS is everithing OK!
2. I had failure with disclosure of sattelits on GPS.
So, the Rom is very good! Thank you for great work!
I've flashed too the P5100 ROM
faorekh said:
1. Phone part does not work. But with SMS is everithing OK!
Click to expand...
Click to collapse
indeed, gives fc: com.android.incallui
Messages and USSD messages (like *100#) are working...
Good work:good:, will post back soon with more findings...
Very good rom ,good work, everysing work's great for me, tank you very much.
Sent from my GT-P5100 using XDA Premium HD app
No Sound
Installed twice (5110), no sound when playing music/movies. Music Player fails to play mp3 files. Any pointers?
John_Br said:
First hickup: YouTube video's won't play
BTW: nice bootlogo. Very smooth and subtile
Grtz,
John
Click to expand...
Click to collapse
wmwamidi said:
Installed twice, no sound when playing music/movies. Music Player fails to play mp3 files. Any pointers?
Click to expand...
Click to collapse
same for me
Also for me (p5110) no such of sound...all the rest is fine
wmwamidi said:
Installed twice (5110), no sound when playing music/movies. Music Player fails to play mp3 files. Any pointers?
Click to expand...
Click to collapse
I think this works for now!
Confirmed no sound on 5110. Looks like the audio.primary.default.so file in /system/lib/hw was omitted when compiling for 5110. Just for the heck of it, I downloaded the 5100 build and the .so file was present in that rom. So, I just took the audio.primary.default.so from the 5100 build and put it in the 5110 build, sound working fine now.
I archived the file in the 5110 zip, then flashed the rom but you can also push the file with a root file explorer. Just make sure to set proper permissions and then reboot for it to take effect.
BoroZG said:
I think this works for now!
Confirmed no sound on 5110. Looks like the audio.primary.default.so file in /system/lib/hw was omitted when compiling for 5110. Just for the heck of it, I downloaded the 5100 build and the .so file was present in that rom. So, I just took the audio.primary.default.so from the 5100 build and put it in the 5110 build, sound working fine now.
I archived the file in the 5110 zip, then flashed the rom but you can also push the file with a root file explorer. Just make sure to set proper permissions and then reboot for it to take effect.
Click to expand...
Click to collapse
Yes It works thanks
egystep said:
Yes It works thanks
Click to expand...
Click to collapse
Simple and smooth, it works perfectly only a small problem with the account on the new browser. Very well. Thank You
.
For all those who so kindly have tested this first beta: :good:
I've taken note of all comments and I am reviewing each and every one of them.
when I've prepared the corrections I'll upload a new version.
I'll try the beta status as short as possible.
:highfive:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
ROMs with Bluetooth Fix!
For several years I have been frustrated with CM and LOS being unable to connect to my car. To compound this, most custom ROMs are based on these ROMs and use the same BT stack making it nearly impossible to find a custom ROM that works with my vehicle. I had assumed that it was hardware driver related until I found that it happened with the Oneplus 3T as well. I was beginning to lose hope.
But thankfully, it turns out that AOSPA uses a different BT stack that actually works with my car, so I spent several weeks researching ROM building and was finally able to build my favorite ROMs with AOSPA's BT stack! I have made a flashable zip using a bluetooth file found in the stock ROM to fix the issues I've been having. The zip is below. If you have a different device and would like this fix feel free to pm me to make a zip or just follow the instructions in post 2 for how to apply the fix in TWRP without a zip.
Disclaimers:
-I only have a Oneplus 3T, not a 3. This zip should work on both, but keep this in mind.
-This will only fix the issues you're having if the ROM you're taking the file from has Bluetooth that works.
BT Fix v1.2
XDA:DevDB Information
[LOS][RR][GZR] Bluetooth Fix for Existing ROMs, ROM for the OnePlus 3
Contributors
shadeau, TheCrazyLex, Thecrazyskull, arter97, xboxfanj, chrislahaye, carlosavignano, arzbhatia, scoobyjenkins, martinusbe, otisman, akhilnarang, varund7726, westcrip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: OOS 4.1.6 or later
Based On: AOSP, LineageOS
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2017-09-20
Created 2017-06-21
Last Updated 2017-11-21
Manual Bluetooth File Replacement Instructions
1) Install the ROM with working bluetooth on your device in TWRP
2) While in TWRP (no need to boot) mount the /system folder
3) Using the file manager navigate to /system/lib/hw, select the bluetooth.default.so file, and tap copy
4) Paste this file somewhere in the base /sdcard directory where it won't be deleted when you factory reset
5) Install your favorite ROM with everything like you normally would/restore it from a backup
6) Mount /system in TWRP again (if it became unchecked or you rebooted)
7) Use the file manager to locate the bluetooth.default.so file that you just placed in your internal memory
8) Copy the file and paste it in /system/lib/hw
9) Reboot and test by connecting to device
10) Enjoy!
Troubleshooting
The flashable zip basically does three things:
1) mounts system partition
2) copies modified bluetooth file to system partition
3) unmounts system partition
4) performs update script like all zips
The zip assumes that your system partition is in the normal location (for a 3T) and formatted in ext4 for my script to work. If you have issues then try manually mounting the system partition with TWRP before flashing the zip.
Reserved2
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Edit: Nevermind. I misunderstood what this was. Still, thank you very much! I cannot wait to try it still!
jbw716 said:
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Click to expand...
Click to collapse
I've built full ROM zips, so you'll need to do a clean install of the ROM that you prefer and you should be good to go. Hope that helps.
Superbbbbbb Thanks, waiting for this fixing for a long time. BT with gear s.3 WORK. Please be keep update.
BTW RR Roms from your file why option in notification slider in additional buttons are difference from the link thread
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
plepew said:
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
Click to expand...
Click to collapse
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
shadeau said:
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Yes, a flashable zip would be the way to go if possible.
I will try Validus on the weekend and report back if I have success... I've installed in in the past and it's nice. But prefer Tesla due to some features.
Thanks for the quick response!
Cheers!!
shadeau said:
I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Should be doable unless framework is involved.
silentvisitor said:
Should be doable unless framework is involved.
Click to expand...
Click to collapse
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Would you be open to posting your sources for these builds?
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Excellent job brother! I too have the same issue with my 2015 Nissan Altima. I honestly have no idea why the makers of these roms don't just use this BT stack...... OOS has no issues with my car, so why don't they all use OOS BT? Just makes no sense to me lol
jbw716 said:
Would you be open to posting your sources for these builds?
Click to expand...
Click to collapse
I'm totally open to that. But I need to figure it how to post to git first .
jbw716 said:
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Click to expand...
Click to collapse
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
shadeau said:
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Click to expand...
Click to collapse
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
shadeau said:
I'm totally open to that. But I need to figure it how to post to git first .
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
Click to expand...
Click to collapse
Here you go. I hope it helps!
https://drive.google.com/file/d/0B22KzlQ3gJRaMHhNbGVDd29JMXM/view?usp=drivesdk
silentvisitor said:
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
Click to expand...
Click to collapse
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
shadeau said:
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
Click to expand...
Click to collapse
Search for "bt" and "bluetooth" in both folders and you'll get list of files. Now extract those files, make a flashable zip and test with some other ROM