Database Info

Any hero roms

That actually have bluetooth stereo working? getting bored flashing my phone back and forward constantly now with no successes, is there any that run? Cheers.
just to add for a 32b. thanks.

It is possible to get stereo bluetooth working.
You can use the ZeroXD or MoDaCo. I feel the ZeroXD is the best one out at the moment. You need the 5.1 version. It's buried within the thread. There are also the instructions to get A2DP working.
I can confirm A2DP is working on the ZeroXD 5.1 release on a 32b device.
I located the post:
http://forum.xda-developers.com/showpost.php?p=4484079&postcount=222
When you follow the instructions for BT make sure you type in all lower case.

naplesbill said:
It is possible to get stereo bluetooth working.
You can use the ZeroXD or MoDaCo. I feel the ZeroXD is the best one out at the moment. You need the 5.1 version. It's buried within the thread. There are also the instructions for pushing the necessary bluetooth files to get A2DP working.
I can confirm A2DP is working on the ZeroXD 5.1 release on a 32b device.
Click to expand...
Click to collapse
The same process can be used on a lot of Hero ROM's.. At this moment, only the 2.x Modaco's based ROM's are not working and they have this files already, so prob unknown!

ricardomega said:
The same process can be used on a lot of Hero ROM's.. At this moment, only the 2.x Modaco's based ROM's are not working and they have this files already, so prob unknown!
Click to expand...
Click to collapse
That is true. But, this is the only rom I've found (so far) that includes a script that enables bluetooth directly from the phone. Are there other roms like this?

naplesbill said:
That is true. But, this is the only rom I've found (so far) that includes a script that enables bluetooth directly from the phone. Are there other roms like this?
Click to expand...
Click to collapse
What do you mean exactly with that enables bluetooth directly from the phone?
Edit: Bluetooth has to be enabled from the phone!

ricardomega said:
What do you mean exactly with that enables bluetooth directly from the phone?
Edit: Bluetooth has to be enabled from the phone!
Click to expand...
Click to collapse
I guess enables is the wrong word. I'm talking about actually enabling it to function. Yes you can turn it on but it doesn't work. There is a fix that requires using ADB to push two additional files. ZeroXD uses a script to make the bluetooth function without the use of ADB push. This same script also changes the rom to function for the myTouch or G1 depending on the option you choose.

is it just me... or do we see this question ALL THE TIME... just saying I'm about 99.9% sure if you took about 5min to look through this forum you would of found your answer...

naplesbill said:
I guess enables is the wrong word. I'm talking about actually enabling it to function. Yes you can turn it on but it doesn't work. There is a fix that requires using ADB to push two additional files. ZeroXD uses a script to make the bluetooth function without the use of ADB push. This same script also changes the rom to function for the myTouch or G1 depending on the option you choose.
Click to expand...
Click to collapse
Ok.. Not all ROM's came defected and depending on this fix.. For instance a very old version of myhero, the v0.0.8 already came with the all the files there. Is not a script, it means that this files were included on the original package. Script is that will follow some command to do a rule.

ricardomega said:
Ok.. Not all ROM's came defected and depending on this fix.. For instance a very old version of myhero, the v0.0.8 already came with the all the files there. Is not a script, it means that this files were included on the original package. Script is that will follow some command to do a rule.
Click to expand...
Click to collapse
It is handled via a script because his rom is for both the dream and the sapphire platforms. You have to run the script to fix wifi and bluetooth depeding on which platform option you choose via the script. I had not seen any other rom with the bluetooth working without using adb push commands. I did notice evil released a rom late yesterday with the bt fix included.

[32A - OLD RADIO] PSFreedom (v3 15/09/2010)

Hello, since there seems to be some confusion I decided to start this thread for the 32A port.
The G1 / Magic 32B thread is here: http://forum.xda-developers.com/showthread.php?t=776922
Note that all the work on PSFreedom was done by KaKaRoTo, and he was helped by DrMon in the MSM72K port, i merely compiled their work and put it in a simple package for everyone to enjoy.
I created 2 packages, an enabler and a disabler, that you have to flash over your working CM 6.0 Final installation.
Flashing the enabler will install the modded kernel and PSFreedom module. You will lose usb functionality completely (no adb, no mass storage etc.) until you flash the disabler.
After flashing the enabler the module will always start upon boot, you have to enter no commands on the terminal emulator.
[SIZE=+2]HOW TO:[/SIZE]
Preliminary: Make sure you are on CyanogenMod 6.0 Final and everything is working correctly. It has been reported that it works also with older CM6 versions and CM5 too, you may try if it works and report it in this thread. If it's the first time, do a Nandroid backup before testing!
Download these files: http://www.multiupload.com/MY1LOGZ6YP (32A-Enabler), www.megaupload.com/?d=3UU2L0UX (32A-Disabler)
Put them on your SD card
Reboot into recovery and Flash Enable_PSFreedom_32A.zip
Reboot
Now psfreedom should be loaded as a module, you will see no difference, except for the loss of normal usb functions.
To run the exploit:
Make sure you are on 3.41 (DO NOT UPDATE OVER THE NETWORK!)
Connect the phone to the PS3 using usb
Turn it off completely (unplug power cable or turn off back switch on Fat models)
Plug it back in (turn on back switch)
Turn it on and immediately press the eject button (you should hear 3 quick beeps)
Booting should take a bit longer (5-10 seconds)
If you see two new options under the games tab, the exploit worked. You can now unplug the phone. Mind that you will have to do this procedure every time you boot your PS3. Try using another USB cable if it doesn't work with a few tries.
To uninstall:
Boot back into recovery
Flash Disable_PSFreedom_G1.zip
Reboot
You should have usb functions back to normal.
Payloads:
This version of PSFreedom contains the new PSGroove 1.1 payload (peek & poke)and is enabled for backups, but backup manager talk should not be done on this thread, there are other boards for that.
If you want to try other payloads (F.I. the new AerialX's apploader), you just have to load it into /proc/psfreedom/payload . You can do it by typing:
Code:
cat payload > /proc/psfreedom/payload
The payload can be wherever you want and has to be in the classic binary format. (just remember to substitute "payload" with the correct path).
Even better, if you put the new payload in the /data/local directory, named "payload" (no quotes), it will be automatically loaded upon startup, thus becoming the default payload.
Mirrors:
Code:
Enabler: http://depositfiles.com/en/files/o1qpcbkeo
http://www.zshare.net/download/80630364707ab8fe/
http://rapidshare.com/files/420315547/Enable_PSFreedom_32A_v3.zip
Disabler: http://www.zshare.net/download/801637791c6185b2/
Versions:
Code:
v0: initial release
v1: +module loaded on startup
+created disabler
v2: updated payload (peek & poke)
v3: resolved bootloop bug, updated PSFreedom, dynamic payload loading.

reserved (10 characters long)

Thanks for yours work!
What about an application to enable/disable psfreedom? Will it be possible in the future?

My Magic (32A) does just reboot over and over after flashing the enabler.......also after flashing the disabler........so now restoring (i ALWAYS back-up befor flashing anything!)
But thanks for trying!

radio version for cm6
one question, CM6 can be for New Radio, or just Old radio?

H3llSp4wN said:
one question, CM6 can be for New Radio, or just Old radio?
Click to expand...
Click to collapse
there's a port also for new radio showthread.php?t=723520
But there are some issues (like broken camera)

Old Radio, new radio requires a different kernel.
For the app, for now psfreedom requires a modded kernel, and it is not possible to switch them on the fly using an app. I know they're working on using a different driver, to avoid having to recompile the kernel. Still don't know if it can be done though.

Can anyone provide a mirror please?

cm6
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards

I always use the vanilla one, straight from the cyanogenMod forums. I think it should work with any of those versions though. Just make sure you're on old radio and you make a nandroid backup before trying.

got everything right now.
thanks for the mirror.

Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try

Hi , just have a question , looked arround with google , couldn't find my answer, maybe someone here knows,
Before trying this out, I would like to know if I can revert my ps3 to original state,
or to how it was before running psgroove?

yes as the exploit must be ran on every boot so simply reboot and delete bxxm

H3llSp4wN said:
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
Click to expand...
Click to collapse
i use redux and it works for me (i still use the release that u have to do thru the terminal)

focus400hp said:
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Click to expand...
Click to collapse
MT3G is 32B, so head off to the Dream section and get that one instead.

with cm6 my g1 go in loop... why?

Hey guys, I'm running into a little trouble after installing the PSFreedom enabler. My htc magic 32a (3.5mm jacket) just sits on the "HTC Magic" screen for eternity after flashing PSfreedom. I do have CM 6.0 installed, I believe its from Cyanogenmod 6.0 S/D version, I don't know what ebi I am nor if need to do something with kernel, but I just know I go into recovery, flash PSfreedom enabler, reboot, the "htc magic" logo shows up and then it sits there forever...Is there something I'm doing wrong?

@ repukken, rock187. You should use the 32B port. The link is in the first post.

Lollipop_Lawlipop said:
MT3G is 32B, so head off to the Dream section and get that one instead.
Click to expand...
Click to collapse
its mt3g slide i believe its different though i did use the precompiled for the dream 32b on a g1 yesterday and works very well and with no probs at all still want to see something for the slide. i asked in the slide forums and everyone just had s*** to talk really

[ROM][17/11/2010] VillainROM G2-DHD v0.1 BETA - Clean senseless ROM

This is a clean rom based on the stock G2 rom, is still only for testing as hasnt been fully tested. ROM Still has a few bugs.
PLEASE POST REPLIES ON VILLAINROM, I MAY NOT SEE THEM ON HERE
Changelog;
v1.0 - Latest
-Initial Release
DOWNLOAD (And screenshots)
Known Issues;
-Camera only works at 3mp (HD Recording does work)
-Dialler adds dashes between numbers
-Screen goes black for a while on first boot
-Bluetooth wont turn on
How to flash;
Method 1;
1: Download ROM Manager from Market
2: Open ROM Manager and select Install ROM From SD
3: Select ROM file and tick options you want (I recommend selecting both)
4: Wait for ROM to flash and phone to reboot
Method 2;
1: Boot into Clockwork Recovery (Hold volume down when turning on phone and select recovery)
3: Select flash zip from sdcard
4: Select ROM file and then confirm
5: Wait for All Done! message
6: A wipe is recommended but not required, if you experience force closes or things not working, try wiping before posting problems.
CLOCKWORK MOD IS REQUIRED TO FLASH AND CAN BE DOWNLOADED HERE
DISCLAIMER - VILLAINROM AND MYSELF ARE NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS ROM, YOU FLASH THIS AT YOUR OWN RISK!
Credits go to - Modaco (For initial ROOT & working Recovery IMG), Kendon (For boot.img), The VillainROM Team, and to everyone who has supported the android development world, i wouldnt be doing this without your support!

First!!
Just flashing now.. will edit this post with my views and constructive criticism
All boots fine and works seemingly well. It has come to my attention that it is are still many G2 remnants such as quick keys in settings and US tmobiles setup page. However something im slightly more interested about is that if you can easily port over a G2 rom could you do the same with a G2 version of CyanogenMod for our DHD's? Feedback would be greatly appreciated on the matter!
Noted bugs:
Quick keys in settings and setup
Bluetooth doesn't activate
No fastboot(could be added?)
Gtalk etc could be removed due to DHD being UK only
Swype doesnt acctually swipe it works as only a standalone qwerty
I will update when i witness more bugs, extensive testing will occur on weekends only ! BTW IT WORKS GREAT + VERY SMOOOTH!!

Works great! It´s very very fast and smoothy...no issues so far...i´m gonna keep an eye in this rom..looking forward new releases!
Kepp going with ur good job!

Excellent work
Possibly my fault but i cant seem to get my bluetooth working ?

im going to try port cyan mod but it seems to be harder than the stock G2 rom for some reason, there are only G2 parts that i cannot remove as they are more embeded than others, this is only a quick port to see how much work needed doing, i will continue to work on it to improve it, if anyone else can confirm bluetooth isnt working and ill look into it

RaiderX303 said:
im going to try port cyan mod but it seems to be harder than the stock G2 rom for some reason, there are only G2 parts that i cannot remove as they are more embeded than others, this is only a quick port to see how much work needed doing, i will continue to work on it to improve it, if anyone else can confirm bluetooth isnt working and ill look into it
Click to expand...
Click to collapse
Im happy to hear you are trying to port over CM6 for the DHD and if you need someone to test roms etc PM me and i am willing to help. If you could add lack of fastboot to the bug list as well, however i was under the impression the g2 should have this anyway, or is it a sense only feature?

RaiderX303 said:
if anyone else can confirm bluetooth isnt working and ill look into it
Click to expand...
Click to collapse
Confirmed. Cant turn it on.
Good job on this one.

Bluetooth fix
Adwinp seems to have fixed bluetooth in his AOSP build so you could ask him how he managed to get it done, probably the same fix is necessary. Obviously all credit to adwinp for establishing the fix.

[ROM][32A][3.22]Stable/Nightly CM 6.1.0 (AOSP 2.2.1) with localized Gingerbread Keyb.

Hi,
just wanted to post my experiences with daily Cyanogenmod-updates.
(I hope this was not covered already...)
There are 3 files which you will need:
cm_dream_sapphire_full-*.zip (http://mirror.teamdouche.net/?device=dream_sapphire)
bc-6.1.0-RC1-ebi1-signed.zip (http://briancrook.ca/android/cm-ports/?C=M;O=A)
gapps-mdpi-tiny-20101020-signed.zip (http://goo-inside.me/google-apps) - optional
All 3 files have to be placed in the sd-card root-folder.
Every morning before I get up I visit http://mirror.teamdouche.net/?device=dream_sapphire with my phone and
download the current nightly build.
Usually it is named: cm_dream_sapphire_full-257.zip where 257 is counted up for each new nightly build.
After downloading I move the file with astro to the root of my sd-card.
Then I switch off my phone and start it in recovery.
-> flash cm_dream_sapphire_full-257.zip
-> flash bc-6.1.0-RC1-ebi1-signed.zip
reboot - done
I have never had a problem with any nightly build yet.
After the flash-reboot I usually uninstall following progs with Titanium Backup:
ADW Launcher (I am using payed LauncherPro Plus)
ROM Manager (as it does not work)
OI Filemanager (I am using astro)
CM Homescreen Info... (pretty useless)
LiveWallpapers (battery/ram/performance eater)
You can find the changelog here when you extract cm_dream_sapphire_full-*.zip:
cm_dream_sapphire_full-*\system\etc\CHANGELOG-CM.txt
Here is how to install the Gingerbread keyboard:
Download your wanted language from here:
http://forum.xda-developers.com/showthread.php?t=864036
extract the archive
You will need:
/system/app/LatinIME.apk
/system/lib/libjni_latinime.so
copy both files to your sdcard/<path>
PHP:
adb shell
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/<path>LatinIME.apk /system/app/
cp /sdcard/<path>/libjni_latinime.so /system/lib/

I remember that there were some problems with the camera in Froyo with 6.35 radio...
Someone fixed them?
[Sorry for my bad English]

Are you sure this is working with the new radio 6.35 and 1.76.2007 SPL?
I tried flashing lastest cm_dream_sapphire_full-*.zip and fails the verification of the SPL.
Let me know if I misread you? On the other hand your signature sayis you're using the old radio...

bc-6.1.0-RC1-ebi1-signed.zip is a kernel designed for old Radio. This will not install on new radio. Please correct the Post title.

Thankyou very muck for info and links

As far as I know, carz and Feeyo are the closest to getting the camera fully functioning with AOSP/CM build for the 32a 6.35 radio.
I have informed Brian Crook and the CM team of our issues. I have also informed some of the kernel devs. I'm hoping they help resolve the camera issues and then produce nightly builds specific to the 32a 6.35. Cyanogen recently said that he is considering splitting and separating out their D/S build into 1 dedicated for the Dream and one for the Sapphire. With luck they will get to this item and produce nightlies for the 32a 6.35.
How sweet would it be to have a fully functioning AOSP/CM rom with nightly builds that can be flashed with no effort on porting????

Yes, sorry it is for the old radio.
updated thread title.
anyway in this rom everything is working stable and fast.
even camera.

anzorb said:
bc-6.1.0-RC1-ebi1-signed.zip is a kernel designed for old Radio. This will not install on new radio. Please correct the Post title.
Click to expand...
Click to collapse
i think anzorb is right this will not work for new radio plz change op

Do you really need to reflash the kernel every time?

lags1974 said:
Do you really need to reflash the kernel every time?
Click to expand...
Click to collapse
yes, otherwise it won't boot.

dhruvnukul said:
i think anzorb is right this will not work for new radio plz change op
Click to expand...
Click to collapse
done.
also updated my sig...

Hey!
Are these roms/builds updates or flashable complete roms?!
I want to see if i can flash it since i want to flash my 32A, 3.22 magic!
If it is, what android version it is?! Sense or non-sence!?
10x

Life Engineer said:
Hey!
Are these roms/builds updates or flashable complete roms?!
I want to see if i can flash it since i want to flash my 32A, 3.22 magic!
If it is, what android version it is?! Sense or non-sence!?
10x
Click to expand...
Click to collapse
yes, it is a full rom (you have to flash also gapps-mdpi-tiny-20101020-signed.zip (http://goo-inside.me/google-apps)).
it is 2.2 without sense.
Cyanogenmod is AOSP....

shadow_empire1 said:
yes, it is a full rom (you have to flash also gapps-mdpi-tiny-20101020-signed.zip (http://goo-inside.me/google-apps)).
it is 2.2 without sense.
Cyanogenmod is AOSP....
Click to expand...
Click to collapse
One thing:
is it stable/reliable?!
I really don't care much about UI, i want a stable and reliable rom; where everything is working good, no reboots, no lags...
BTW is this rom fast?! (quadrant score for example)
10x

yeah, its a good rom, just flashed it myself, im using launcherpro, seems fine

Guys, after flshing this rom, i have APN for GPRS and MMS, but my phone won't connect to 3G at all nor to send mms.
Is it possible that it takes to much time to connect at first?
also in Phone Informations it is WCDMA prefered, and 0.0.0.0 Not Allowed ..
also, browser is down (can't open any page)
and can't send SMS (instant Message sending failed)
Any help?

Life Engineer said:
One thing:
is it stable/reliable?!
I really don't care much about UI, i want a stable and reliable rom; where everything is working good, no reboots, no lags...
BTW is this rom fast?! (quadrant score for example)
10x
Click to expand...
Click to collapse
for me it is the perfect rom.
everything is working stable and fast.
quadrant benchmark: 271
CPU: 688
Memory: 188
I/O: 167
2D: 143
3D: 176

I was using alans rom, but it's a piece of garbage and doesn't work (all my calls go straight to voice mail 75% of the time).
Can I use this with the 3.something radio? Or do I need he new 6.35.something radio?
I have the 3 one.

Unfortunately it was VERY unstable for me, it crashed 4 times in one hour, each time requiring me to remove the battery. Back to stock Rogers 2.1.

keinengel said:
Unfortunately it was VERY unstable for me, it crashed 4 times in one hour, each time requiring me to remove the battery. Back to stock Rogers 2.1.
Click to expand...
Click to collapse
I can not agree...
I am using it since 1-2 months without any problem...
did you wipe/flash?

[LOS][RR][GZR] Bluetooth Fix for Existing ROMs

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