Are there any KitKat ROMs with working A2DP? - Sony Xperia P, U, Sola, Go

I have snooped around for a while in the development part of this forum, but it seems like either A2DP is listed as non working, or it's just not mentioned. Are there any KitKat ROMs with it working? I would like to upgrade my wife's phone to something better than the last official ROM, and I'm very satisfied with KitKat on my own devices, but she uses her phone in her car to play music through the BT enabled stereo, so it needs A2DP. If none are working now, is there a chance to get something that's working with A2DP in the near future?

Mastiff said:
I have snooped around for a while in the development part of this forum, but it seems like either A2DP is listed as non working, or it's just not mentioned. Are there any KitKat ROMs with it working? I would like to upgrade my wife's phone to something better than the last official ROM, and I'm very satisfied with KitKat on my own devices, but she uses her phone in her car to play music through the BT enabled stereo, so it needs A2DP. If none are working now, is there a chance to get something that's working with A2DP in the near future?
Click to expand...
Click to collapse
There is not KitKat ROM with working A2DP. It will be fix but not in the near future.

OK, thanks a lot! Then I won't have to look in vain. Any idea how far that future is?

Mastiff said:
OK, thanks a lot! Then I won't have to look in vain. Any idea how far that future is?
Click to expand...
Click to collapse
Hi,
percy wrote in his thread, that he's working on A2DP,wifi direct and other stuff and only problem will remain FM radio. But he also wrote that he's now busy with studies till 10th of april or so. After then he will release new kernel with dual recovery and maybe weekly 5 release ...

OK, then I'll wait a month or so for that. Thanks!

Mastiff said:
OK, thanks a lot! Then I won't have to look in vain. Any idea how far that future is?
Click to expand...
Click to collapse
Some, or maybe all, CM KitKat ROMS use Bluez for Bluethooth. At present, bluetooth is working fully on these roms, except music streaming through A2DP. Exactly what you need.
I assume it'll be fixed in next release of Bleuz, which will be version 5.17 (yo can follow this on www.bluez.org). A week after the release of this version from Bluez - we'll most probably have the first KitKat Roms with bluethooth fully operational.

Beverke said:
Some, or maybe all, CM KitKat ROMS use Bluez for Bluethooth. At present, bluetooth is working fully on these roms, except music streaming through A2DP. Exactly what you need.
I assume it'll be fixed in next release of Bleuz, which will be version 5.17 (yo can follow this on www.bluez.org). A week after the release of this version from Bluez - we'll most probably have the first KitKat Roms with bluethooth fully operational.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-u/general/aosp-xperia-p-sola-t2684583
Your only solution but you have to wait some weeks!

Thanks, mate! Thread subscribed. I'm sure my wife can wait a few weeks, especially since I haven't told her about it yet. Much easier to tell her "time to update your phone, honey" than "in a few weeks or months it may be possible to update your phone, honey".

Mastiff said:
Thanks, mate! Thread subscribed. I'm sure my wife can wait a few weeks, especially since I haven't told her about it yet. Much easier to tell her "time to update your phone, honey" than "in a few weeks or months it may be possible to update your phone, honey".
Click to expand...
Click to collapse
Hahaha you are always welcomed! You did the best thing :good:

@Mastiff
Go to bluez.org
All KitKat roms on this forum use it as their Bluetooth stack. When they list a2dp as working it will work.

Thanks! But according to them, on the 11th of March:
"On the Android side by far the biggest feature addition is full support for A2DP 1.3 and AVRCP 1.5. Several other profiles, such as HFP and GATT have continued receiving a fair amount of patches as well, but they are not considered complete yet."
So that should mean that it's already working and has done so for almost a month. Or do I misunderstand it?

Our plaform is tricky. Is not enought BlueZ support (they work on Nexus devices) we need adapt our platform to BlueZ, because old Sony code is deprecated

OK, thanks. A bit more complicated than Hamza thought, then. Well, I'll probably just have to wait a bit longer.

Any news after 2 months?
Sent from my Xperia U using XDA Free mobile app

Yeah, one month ago I got tired of waiting and bought an Xperia Z1 Compact for my wife... She actually took to the size quite easily, I thought it would be too big for her, but I guess the P had sort of primed her for it. Unlike the the P om it's final stock ROM the Z1 Compact on KitKat is very stable.

Related

[Q] Is there a vanilla 2.2 ROM?

Hey guys,
I've spent a lot of time here on XDA and around the internet and I can't seem to find an answer to my problem. I've been looking for a week or so, on and off.
I really would like to use my Vibrant for some mobile gaming, including some of the emulators that are available on the Market. What I would like to do is use the Wiimote Controller application alongside the emulators, because I never feel very comfortable using a touch-screen game pad.
The trouble is that for some reason, Samsungs Galaxy S line of phones will not sync up with the Wii Remote via Bluetooth. Most if not all HTC devices have been able to sync up, so I know the Wii Remote is capable of it. I spoke to the developer of the application and he said that for some reason the SGS line of devices just won't do it. He suggested a while back that flashing a stock-Android ROM should solve that problem.
My question, then, would be is there a Vanilla ROM based on 2.2 or do you guys know of a ROM that will accomplish what I'm going for? Right now I am using Frankin-TWIZ by Eugene and I love the ROM but the Wii Remote problem is still there.
So, I appreciate any advice and suggestions that you guys can offer and I do apologize if a similar thread has been started elsewhere, I really couldn't find anything.
Thanks so much,
Nate
Vanilla 2.2 will not help you here. The problem is in the Samsung implementation of Bluetooth. Bluetooth v3.0 + HS is on the virge of existence, but is not yet a fully ratified standard. Samsung used this fact to be able to release a device they call Bluetooth 3.0, but since there is no standard yet they can do whatever they want with. Apparently what they wanted was to not support Bluetooth game controllers.
T313C0mun1s7 said:
Vanilla 2.2 will not help you here. The problem is in the Samsung implementation of Bluetooth. Bluetooth v3.0 + HS is on the virge of existence, but is not yet a fully ratified standard. Samsung used this fact to be able to release a device they call Bluetooth 3.0, but since there is no standard yet they can do whatever they want with. Apparently what they wanted was to not support Bluetooth game controllers.
Click to expand...
Click to collapse
So, I'm assuming there is no way for a Samsung Galaxy S device to use an older implementation of Bluetooth?
Thank you for your help, I really do appreciate it, this has been bugging me for a while haha
You should be able to gleam more information from this thread:
http://forum.xda-developers.com/showthread.php?t=746489
I am not saying that it is not possible, just that the ROM is not the issue, but rather the Bluetooth implementation is. It almost feels as if Samsung did this intentionality.
As far as I am aware all the ROMs here are based off either Samsung source or Samsung leaks. A TRULY vanilla ROM to get the original Bluetooth implementation would mean building it from Google source, which would be sans drivers and you would need to make everything work with your hardware by building your own drivers. I don't think you are going to find this just yet.
You could try CM 6.1, but it is not stable or final yet on the vibrant and I don't really know if it fixes the Bluetooth issue.
Everything works great with my MotoROKR S305 Stereo Bluetooth Headset, and that is all I really care about.
T313C0mun1s7 said:
Vanilla 2.2 will not help you here. The problem is in the Samsung implementation of Bluetooth. Bluetooth v3.0 + HS is on the virge of existence, but is not yet a fully ratified standard. Samsung used this fact to be able to release a device they call Bluetooth 3.0, but since there is no standard yet they can do whatever they want with. Apparently what they wanted was to not support Bluetooth game controllers.
Click to expand...
Click to collapse
T313C0mun1s7 said:
You should be able to gleam more information from this thread:
http://forum.xda-developers.com/showthread.php?t=746489
I am not saying that it is not possible, just that the ROM is not the issue, but rather the Bluetooth implementation is. It almost feels as if Samsung did this intentionality.
As far as I am aware all the ROMs here are based off either Samsung source or Samsung leaks. A TRULY vanilla ROM to get the original Bluetooth implementation would mean building it from Google source, which would be sans drivers and you would need to make everything work with your hardware by building your own drivers. I don't think you are going to find this just yet.
You could try CM 6.1, but it is not stable or final yet on the vibrant and I don't really know if it fixes the Bluetooth issue.
Everything works great with my MotoROKR S305 Stereo Bluetooth Headset, and that is all I really care about.
Click to expand...
Click to collapse
I'll take a look at that thread, and I just wanted to say that I really appreciate you taking the time to help me out here.
If there's anything I can do for you to return the favor, please don't hesitate to ask. Thanks again

Does i9000 rom mean we are one step closer?

.....to having a working Gingerbread rom for the Vibrant? Is this rom going to contain the keys to getting a fully functional build?
One can only hope.
Sent from my T959 using XDA App
We already have 3+ gingerbread roms from a month ago... Why do you want a build that will take longer? The devs can probably put the features from it to ours but that may be it, the remove service.jar won't work I dont think so.
according to the samsung site Vibrant is to be supported through a 2.3 gingerbread release, but then that is the Samsung site and they probably release 2.3 after we all moved on to something else. One of the problems most phone manufacturers of android have discovered, is how quickly the upgrading demand is. They did not anticipate that we the public would get so savvy so fast.
But My guess 2.3 release will be in Aug-Sept after the S2 release
Official i900 rom rolling out already!!!
http://www.engadget.com/2011/04/16/galaxy-s-gingerbread-update-now-rolling-out-across-europe/
Isn't cm7 2.3.3?
dcaples002 said:
Isn't cm7 2.3.3?
Click to expand...
Click to collapse
CM7 and MIUI are 2.3.3 yes.
dcaples002 said:
Isn't cm7 2.3.3?
Click to expand...
Click to collapse
yes, but OP is asking if this recent leak means we're going to get a FULLY FUNCTIONAL rom soon.
asdf916 said:
yes, but OP is asking if this recent leak means we're going to get a FULLY FUNCTIONAL rom soon.
Click to expand...
Click to collapse
"Fully Functional"
Nope, never.
Most of our GPS sucks, and if GPS isn't included its not a "fully functional" rom.
so in theory, no we will never have it.
xriderx66 said:
"Fully Functional"
Nope, never.
Most of our GPS sucks, and if GPS isn't included its not a "fully functional" rom.
so in theory, no we will never have it.
Click to expand...
Click to collapse
GPS works fine for some people, even without the hardware fix. So don't say we'll never have it, unless you have some insider info the rest of us don't have. This release probably won't get us any closer, but who's to say we won't get a 2.3 release for our phones. Samsung isn't as horrible at updates as we used to think. Most phones released prior didn't see it past one major update. Samsung has pushed out two major updates for a phone that's coming up on its 1st birthday. Can't say the same for many other OEMs.
thegreatcity said:
GPS works fine for some people, even without the hardware fix. So don't say we'll never have it, unless you have some insider info the rest of us don't have. This release probably won't get us any closer, but who's to say we won't get a 2.3 release for our phones. Samsung isn't as horrible at updates as we used to think. Most phones released prior didn't see it past one major update. Samsung has pushed out two major updates for a phone that's coming up on its 1st birthday. Can't say the same for many other OEMs.
Click to expand...
Click to collapse
I didn't say GPS doesnt work for ALL, but be truthful, most of the GPS of Vibrants do not work, and probably wont work until you do the hardware fix or get another vibrant made at a earlier date.
I wasn't talking about updates directly from Samsung, and i've never questioned their update-mentality. I receive updates on my Samsung TV/Blu-Ray player i bought a year ago still.
I was talking about a "FULLY FUNCTIONAL" rom.
Most of the roms we already have, GPS doesn't work for most, so what makes you think it'll randomly work when we get 2.3? A Software update isn't going to do much except make it about 50 ft accuracy or something like that.
xriderx66 said:
I didn't say GPS doesnt work for ALL, but be truthful, most of the GPS of Vibrants do not work, and probably wont work until you do the hardware fix or get another vibrant made at a earlier date.
I wasn't talking about updates directly from Samsung, and i've never questioned their update-mentality. I receive updates on my Samsung TV/Blu-Ray player i bought a year ago still.
I was talking about a "FULLY FUNCTIONAL" rom.
Most of the roms we already have, GPS doesn't work for most, so what makes you think it'll randomly work when we get 2.3? A Software update isn't going to do much except make it about 50 ft accuracy or something like that.
Click to expand...
Click to collapse
GPS doesn't work on the new 2.3 roms because we don't have drivers, it's a software issue. That will ABSOLUTELY change with an official release. For those with working GPS,(such as me, others who have done the hardware fix, and people who got lucky with revised Vibrant hardware) this WOULD be a fully functional rom.
I didn't say the update would magically fix a hardware problem, but the fact is the GPS issues have nothing to do with the rom, only the hardware. However with CM7, it is an issue with the rom. That's why GPS works for no one, when it worked fine on 2.2 for those without hardware issues. There is a difference between a crippled rom and crippled hardware.

Is GB or HB it?

Very bored with the OS on my View 4G..
Any options for ICS? I need STABLE.. this is in my car as nav and multimedia, so it needs to be extremely stable.
There's no Stable ROM For Ics.
GB or HC
R0flC0pt3r said:
There's no Stable ROM For Ics.
Click to expand...
Click to collapse
I got tired of using gingerbread and wanted the USB Device Host feature so i can use my ps3 controller.
Installed Dexters Jellybean 1.7 , works great except, you cant make phone calls anymore.
3G works for web/ remote desktop, but once u call someone, theres no audio back and forth.
Gonna try a work around so i can use voip / call forwarding.
Middl3man said:
I got tired of using gingerbread and wanted the USB Device Host feature so i can use my ps3 controller.
Installed Dexters Jellybean 1.7 , works great except, you cant make phone calls anymore.
3G works for web/ remote desktop, but once u call someone, theres no audio back and forth.
Gonna try a work around so i can use voip / call forwarding.
Click to expand...
Click to collapse
I believe the wired mic option works with Dex' build.
Hmm. Might have to check it out. Did you install on a View or Flyer?
R0flC0pt3r said:
There's no Stable ROM For Ics.
Click to expand...
Click to collapse
and jellybean too
No stable ics or jb rom? Not sure I agree with that statement. I recently installed YNC's CG rom, and it's been at least as stable as HTC's honeycomb build. Granted I haven't yet put the GPS or bluetooth through a good workout (both crucial to a setup in a car), but for everyday use around the house it has been rock solid.
rickwood said:
No stable ics or jb rom? Not sure I agree with that statement. I recently installed YNC's CG rom, and it's been at least as stable as HTC's honeycomb build. Granted I haven't yet put the GPS or bluetooth through a good workout (both crucial to a setup in a car), but for everyday use around the house it has been rock solid.
Click to expand...
Click to collapse
can you give me the link? i wanna try it
There are still a few features yet to be implemented: front facing camera, usb otg, and a couple of others. So read the first post to see the full list of things that aren't yet functional. But if (like me) you don't ever use one of those features, this build is very good (and has been extremely stable for me). Here's the link:
http://forum.xda-developers.com/showthread.php?t=1673430

[Q] FM radio on roms

any hope of getting FM radio support on roms (I'm mainly using cyanogenmod, usually sportsstar's). I've tried the port of the apk for the fm radio (wouldn't run) and some spirit radio apk (loud static all channels). Thanks.
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
yeah. ok thanks, I guess I will try again.
your welcome
reebokhcfr said:
yeah. ok thanks, I guess I will try again.
Click to expand...
Click to collapse
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
chevycowboyusa said:
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
Click to expand...
Click to collapse
Sense Apps do not work on AOSP roms. And can't be made to work...
FM Radio
dcacklam said:
Sense Apps do not work on AOSP roms. And can't be made to work...
Click to expand...
Click to collapse
Hi Dave! Thanks for the response
I thought there was an FM radio app in the CM Builds??
There are people using Spirit on CM10 (other devices) and I have got Spirit working on Sense 4 (even though the built in one doesn't work)
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
mgp53 said:
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
Click to expand...
Click to collapse
I couldn't get it to work either on the PacMan rom
I just flashed SpeedRom 9.0 Beta 1 and the FM Radio app works because SpeedROM is still a sense based ROM but looks like JellyBean.
Viper Radio
chevycowboyusa said:
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
kodunmit said:
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
Click to expand...
Click to collapse
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Firmware
JimDandy68 said:
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Click to expand...
Click to collapse
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
chevycowboyusa said:
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
Click to expand...
Click to collapse
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
JimDandy68 said:
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
Click to expand...
Click to collapse
Just want to ask again on this thread, has anyone ever gotten Spirit FM or another FM radio apk to work on a JB ROM (non-sense-based)? Chevy mentioned the Spirit FM 3rd beta, but not sure whether he was talking about having it work on a JB ROM or on Viper. ICS ROMs mostly have the stock radio app working, so not an issue there.
Thanks.
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Odysseus1962 said:
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Click to expand...
Click to collapse
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
JimDandy68 said:
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
Click to expand...
Click to collapse
I know what you're talking about. I think many here, myself included, wish that development was further along. Frankly, I find it sad and ironic that my old HD2, which was a Windows phone, has had fully functional usable stable Jellybean ROMs for a well over a year and it never had any sources released to develop from.
The sad truth is that the Amaze is a great device that wasn't marketed well, so few units were sold. Too few at least for it to have developed a devoted loyal following. If you follow the threads you see that there was never a large volume of development for it and that most of the early adopters have long since moved on to other devices. I'm just glad that we're now experiencing a second wave with new folks stepping up and trying.
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Odysseus1962 said:
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Click to expand...
Click to collapse
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
JimDandy68 said:
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
Click to expand...
Click to collapse
I wouldn't be so down on HTC. They may not have been the most supportive manufacturer when it comes to outside development, but they've also produced some of the most groundbreaking innovative products. They're in financial trouble now, as their market share has eroded, and haven't had a breakout device in some time. They realize this and have begun making incremental improvements within the development community in an attempt to improve it's perception. The thing is who are you going to jump ship to? Samsung is already undermining android by developing Its own market place for apps that can only run on their devices and has announced It's developing its own proprietary OS. Since they're the biggest player in this device market, they could easily splinter Android and force other manufacturers to do the same to compete.
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Odysseus1962 said:
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Click to expand...
Click to collapse
Point taken. I'm 45 and evidently haven't learned anything. :cyclops:
Time to go back to a landline.

How to unpack bluetooth driver from a KitKat rom and install it into a Nougat?

I've bought a Kindle Fire HDX 7 thor and it was pre-installed a CM11 by the shop and back then it CAN connect with my Samsung level U bluetooth headset but after installing four different roms on the page https://forum.xda-developers.com/kindle-fire-hdx I found out that my bluetooth and my front camera are all unuseable.
I just want to ask why and how I can use bluetooth on it?
Thankyou.
BTW I'll upload the zip file I got from the seller online and post link later.
THANK YOU
Now I am using Aosp from https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-aospextended-t369113
The file that seller gave me is on MEGA https://mega.nz/#!5CQQXbia with no password.
BobLao said:
Now I am using Aosp from https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-aospextended-t369113
The file that seller gave me is on MEGA https://mega.nz/#!5CQQXbia with no password.
Click to expand...
Click to collapse
Me thinks that ain't gonna work. If it were that simple the ongoing BT issues with this device would have been solved long ago. The same core developers have been working with both HDX variants since the Jelly Bean days. Up until recently BT was unreliable on all non-KitKat based custom ROMs. A lot of work went into resolving the issue w/o success. Some Kernel tweaks that came along with LOS seemed to improve things; now *most* devices will pair although it's not always a smooth experience. Not sure what the issue is with your Samsung headset.
Front camera is a different issue as that has not proven to be problematic once a 3rd party camera app is installed...at least on 7" models (thor). Possible you have a hardware issue.
Davey126 said:
Me thinks that ain't gonna work. If it were that simple the ongoing BT issues with this device would have been solved long ago. The same core developers have been working with both HDX variants since the Jelly Bean days. Up until recently BT was unreliable on all non-KitKat based custom ROMs. A lot of work went into resolving the issue w/o success. Some Kernel tweaks that came along with LOS seemed to improve things; now *most* devices will pair although it's not always a smooth experience. Not sure what the issue is with your Samsung headset.
Front camera is a different issue as that has not proven to be problematic once a 3rd party camera app is installed...at least on 7" models (thor). Possible you have a hardware issue.
Click to expand...
Click to collapse
So there is no way for me to use bluetooth on my non-KitKat custom rom right?
Well thanks mate
BobLao said:
So there is no way for me to use bluetooth on my non-KitKat custom rom right?
Well thanks mate
Click to expand...
Click to collapse
Apparently on *your* HDX with a specific BT device. Most are reporting good BT pairing results with the latest Nougat ROMs. Given the front camera also has issues you may have scored a defective device.
BobLao said:
So there is no way for me to use bluetooth on my non-KitKat custom rom right?
Well thanks mate
Click to expand...
Click to collapse
Davey126 said:
Apparently on *your* HDX with a specific BT device. Most are reporting good BT pairing results with the latest Nougat ROMs. Given the front camera also has issues you may have scored a defective device.
Click to expand...
Click to collapse
FWIW - you might find this post helpful: https://forum.xda-developers.com/showpost.php?p=74757593&postcount=88
Davey126 said:
FWIW - you might find this post helpful: https://forum.xda-developers.com/showpost.php?p=74757593&postcount=88
Click to expand...
Click to collapse
Thank You

Categories

Resources