Related
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
anyone know where a guy could get the htc fm radio app???
Aldo101t said:
anyone know where a guy could get the htc fm radio app???
Click to expand...
Click to collapse
I tried installing the FM Radio app from my original Dinc, and it installed just fine, opened, showed the radio screen, and then crashed, and won't go any further than that now. Could be because that ROM was de-odexed, but I doubt it.
Have you tried pulling it from the Dinc 2 or Evo 4G Shift? I'm going to try to pull it from a HTC One S ROM if I can find one, since it's so similar to the Dinc 4G.
IceDragon59 said:
I tried installing the FM Radio app from my original Dinc, and it installed just fine, opened, showed the radio screen, and then crashed, and won't go any further than that now. Could be because that ROM was de-odexed, but I doubt it.
Have you tried pulling it from the Dinc 2 or Evo 4G Shift? I'm going to try to pull it from a HTC One S ROM if I can find one, since it's so similar to the Dinc 4G.
Click to expand...
Click to collapse
IC TAZZ rom is a one s rom but a custom rom, it was ported to the inc2
they are all system apps, thats the problem
maybe this phone doesn't have the hardware to run it
I tested FM radio and it does not work.
blazingwolf said:
I tested FM radio and it does not work.
Click to expand...
Click to collapse
The FM Radio on the HTC One S ROM I found didn't work, either.
Makes me wonder if the hardware is in place to run something like this. It uses your headset as an antenna which would seem like some hardware would need to be implemented and with the phone not having the software as stock just makes me wonder.
*Madmoose* said:
Makes me wonder if the hardware is in place to run something like this. It uses your headset as an antenna which would seem like some hardware would need to be implemented and with the phone not having the software as stock just makes me wonder.
Click to expand...
Click to collapse
Quite the possibility. I don't ever listen to the radio, but I noticed it was missing when I got the phone.
anyone try that spirit fm app, looks like it's for rooted phones, but is supposed to work on stock.
IceDragon59 said:
Quite the possibility. I don't ever listen to the radio, but I noticed it was missing when I got the phone.
Click to expand...
Click to collapse
i used it all the time on the inc2, i miss it now
*Madmoose* said:
Makes me wonder if the hardware is in place to run something like this. It uses your headset as an antenna which would seem like some hardware would need to be implemented and with the phone not having the software as stock just makes me wonder.
Click to expand...
Click to collapse
As far as I can tell this is correct.
blazingwolf said:
As far as I can tell this is correct.
Click to expand...
Click to collapse
i don't know, i think nits rom has fm radio,i think, so the hardware must be there.it's based on stock
Aldo101t said:
i don't know, i think nits rom has fm radio,i think, so the hardware must be there.it's based on stock
Click to expand...
Click to collapse
It was there because he added it. It's one of the ways that I tested FM radio.
However, if you want to mess with it have at it.
blazingwolf said:
It was there because he added it. It's one of the ways that I tested FM radio.
Click to expand...
Click to collapse
ok, you mean the app didn't work on nits rom, well then i'd say the hardware is not there then
blazingwolf said:
It was there because he added it. It's one of the ways that I tested FM radio.
However, if you want to mess with it have at it.
Click to expand...
Click to collapse
i can't i'm still locked up
So, anyone have any luck getting fm radio to work? It sounds like the hardware isn't there, but I'm still holding out hope.
Sent from my ADR6410LVW using xda app-developers app
There is definitely hardware for FM radio. Whether there is any software that can utilize it is still unknown (at least to me).
I don't have root yet but when I do that's one of my goals - to get the FM tuner working.
xdadevelopers-user said:
There is definitely hardware for FM radio. Whether there is any software that can utilize it is still unknown (at least to me).
I don't have root yet but when I do that's one of my goals - to get the FM tuner working.
Click to expand...
Click to collapse
Yes, the chip is capable of FM. However, everything else seems to be missing. As noted in this thread I tried several things to get it working and it didn't.
Aldo101t said:
anyone try that spirit fm app, looks like it's for rooted phones, but is supposed to work on stock.
Click to expand...
Click to collapse
Spirit Free is here: http://d-h.st/P5Y .
I've had debug logs from two un-rooted users, but nobody has ever sent one from a rooted device, and I'd be interested to see. My sales stats actually show 6 people with this phone, but it seems many people don't even get in touch with me if it doesn't work. I may disable this device in Play and see if anyone notices.
Use Menu-> Test-> Email-> Logs and after 20 seconds or so press Send.
AFAICT, the FM/Bt/WiFi combo chip is the same WCN3660 on the AT&T OneX / OneXL LTE/ OneS / Evo 4G LTE and some new Motorolas.
AFAIK, nobody knows if the FM antenna pin(s) are connected to the wired headset circuitry for use as the FM antenna. If so, then software may be able to enable FM.
BUT, like the new Motorola's (Razr HD, M ?) it appears that the firmware/ROM is not set up to enable FM, perhaps via some config option that Qualcomm provides.
So I think a custom kernel and/or ROM will be required to even see if FM is hardware possible.
Or, with SU/root we may get lucky and be able to load the radio-iris loadable kernel driver and get it working. Getting it loaded at least is the main thing needed to get further info.
mikereidis said:
Spirit Free is here: http://d-h.st/P5Y .
I've had debug logs from two un-rooted users, but nobody has ever sent one from a rooted device, and I'd be interested to see. My sales stats actually show 6 people with this phone, but it seems many people don't even get in touch with me if it doesn't work. I may disable this device in Play and see if anyone notices.
Use Menu-> Test-> Email-> Logs and after 20 seconds or so press Send.
AFAICT, the FM/Bt/WiFi combo chip is the same WCN3660 on the AT&T OneX / OneXL LTE/ OneS / Evo 4G LTE and some new Motorolas.
AFAIK, nobody knows if the FM antenna pin(s) are connected to the wired headset circuitry for use as the FM antenna. If so, then software may be able to enable FM.
BUT, like the new Motorola's (Razr HD, M ?) it appears that the firmware/ROM is not set up to enable FM, perhaps via some config option that Qualcomm provides.
So I think a custom kernel and/or ROM will be required to even see if FM is hardware possible.
Or, with SU/root we may get lucky and be able to load the radio-iris loadable kernel driver and get it working. Getting it loaded at least is the main thing needed to get further info.
Click to expand...
Click to collapse
Log sent. No luck on anything working though. There is no sound of static even so I can't tell if it is even trying. I have also tried other FM apps from HTC with no luck. I have no idea how to tell if the antenna pins are connected though I would be happy to try if told how.
Let me know if the logs help.
blazingwolf said:
Log sent. No luck on anything working though. There is no sound of static even so I can't tell if it is even trying. I have also tried other FM apps from HTC with no luck. I have no idea how to tell if the antenna pins are connected though I would be happy to try if told how.
Let me know if the logs help.
Click to expand...
Click to collapse
Thanks ! Nice to finally see with SU.
With SU your radio-iris-transport FM driver is successfully loaded.
Spirit detect and uses the HTC OEM Proprietary FM API. The problem there is that RSSI values are 0 or -128, a bad sign.
But there is still hope with the low level API.
Set Menu-> Settings-> FM API to "Low Level" and restart Spirit.
For audio, the default setting (Auto) of Audio-> Method is translated to "HTC", which is for stock HTC devices. That seems to be getting translated to the proper audio ALSA control settings. But if you lack any audio, setting Audio-> Method to "HTC OneX ALSA" or even "HTC OneX QCom" might help.
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.
Not sure I'm using the correct terminology there, but I've read that the latest OTA update fixes a bluetooth issue. Was hoping it fixes the issues I've seen with random connection dropping between the phone and my bluetooth piece.
I've also read the new update breaks root as well as several people reporting poor battery performance after updating. So, was curious if anyone has just the bluetooth fix in a flashable file?
If you want to experiment, the second post in my kernel thread has a link to a kernel built using the stock Linux Bluetooth drivers instead of the HTC drivers. I would be curious to know if it fixes your or not problems.
Ah, nice. I will definitely look into it.
Do you know what else that OTA update supposedly fixes?
No idea. Waiting for the kernel source to see if anything was fixed there. No way to tell what they changed outside of the kernel.
oh so that was HTC's doing. I bought a cheap audio dongle to connect my phone to my car stereo and it works great, but every now and then the signal drops, so I chalked that up to my cheap Chinese adapter, not the phone.
I have a similar Probem, whenever I want to connect my DNA with the car radio, I always have to enter the code again, which is very annoying, have the 2:04 update on it was also previously with 1.15.605.2, maybe someone has an idea?
So after many people telling me that the only way to accomplish what I want is to root...I did. For the first time ever, in over 5 years of Android ownership. So will itemize the issues at at hand and ask relevant questions and state what I have done within each one. But first, you should know I rooted using this method http://forum.xda-developers.com/showthread.php?t=2026938 and I have SuperSU version 1.25, and still running stock ROM and I am S-On.
Issue 1: Wifi tether.
I have downloaded Wifi Tether version 3.2 Beta 2 and I got it to work. The issue is, is there a better performing app or a way to get this one to perform faster? I get about 2mbps on speedtest.net on my phone while the tethered devices get 0.72mbps..I want to get the same on both. Anybody know how?
Issue 2: LTE connectivity.
Many know the LTE connectivity on LTE Evo sucks the big one. So now that I am rooted, what can I do to improve it? Specific ROM? Specific App? custom radio drivers?
Issue 3: Bluetooth
Within my 3 questions here, I am obviously also asking for ROM recommendations, but I have heard certain ROMs break bluetooth and I wanna avoid that at all costs. But the real issue is not the latter. My concern is AVRCP bluetooth profile. I need it to be version 1.3 or higher in order for my phone to send track/album art info to my car's Display Audio/Navigation screen. This is something I have been trying to figure out for years, I posted many threads on this here http://forum.xda-developers.com/showthread.php?t=1728786 and here http://forum.xda-developers.com/showthread.php?t=1702047 and also here http://forum.xda-developers.com/showthread.php?t=1553950
The difference is that back then, I was not willing to root, but now, I'm already rooted.
So shoot me some solutions, and forever change my life! O well respected community of android tinkerers!
Now for issue 3 (bluetooth), if you guys know a way to get this issue http://forum.xda-developers.com/showthread.php?t=1702047 to work, that would also help me. Here is the OP post quoted
darkleafar said:
So I just recently upgraded from an Evo 3D to the Evo 4g LTE, and the phone is gorgeous and all, but I've lost a major feature and it is scaring the hell out of me, I hope you guys can help:
Intro to my problem:
I have a 2012 Prius V, which has built in Bluetooth and an USB port. My Evo 3D lacked the right level of bluetooth AVRCP profile needed in order to display track names, artwork, etc, on my Prius Nav screen through bluetooth. So to work around that, I would plug in my Evo 3D into the Prius's USB port, then I would select "Disk drive/USB mass storage mode" on the phone and voila! My car saw all my music, complete with track names, album artwork, etc.
My main problem:
All of my music is in my 16GB MicroSD card, so I figured just putting it into my new LTE Evo would suffice...but it didnt. When I plug in my LTE Evo, the "Disk drive/USB mass storage mode" NO LONGER triggers my car detecting it. I noticed a new option, called "Media Sync." Selecting that WILL trigger my car dectecting the phone storage, but it ONLY detects the BUILT IN phone storage, not what's on my MicroSD card.
What's even worse...
Also, if you are wondering, the LTE Evo, despite having Bluetooth 4.0, STILL DOES NOT have the right level of AVRCP needed to display album artwork and track names over bluetooth. I was very, extremely disappointed when I realized this. I ve always been a loyal Anti-Apple/Pro-Windows/pro-Android kinda tech guy, but how come Iphones have been able to do this (track names and album artwork over bluetooth) for several years and this new super phone of ours cannot?
Where I need your help:
How can I make it so that my car can recognize my MicroSD card, not just my phone's storage?
I'm not gonna be forced to stick my music into my phone's built in storage instead of my MicroSD card, am I?
Isnt there any software/firmware or mods/rooting stuff I can do to enable tracknames and album artwork over bluetooth on this phone, since it already has bluetooth 4.0 after all?
Well, thank you very much for your time and I hope y'all have some awesome answers, more than greatly appreciated.
Click to expand...
Click to collapse
1.MeanBean Rom I get awesome tether speeds
2. Known issue there is no fix
3. MeanBean Rom
Sent from my EVO using xda premium
scoot0073 said:
1.MeanBean Rom I get awesome tether speeds
2. Known issue there is no fix
3. MeanBean Rom
Sent from my EVO using xda premium
Click to expand...
Click to collapse
So you know for a fact MeanBean ROM will fix both bluetooth AVRCP profile issue and Wifi tether speeds? Cuz if so, sir, you just made my day!
darkleafar said:
So you know for a fact MeanBean ROM will fix both bluetooth AVRCP profile issue and Wifi tether speeds? Cuz if so, sir, you just made my day!
Click to expand...
Click to collapse
Mean bean fixes only your #1 issue...
1.3 AVCRP Bluetooth profile is not available even on a custom kernel, since meanbean uses stock kernel with elemental X over clock modules, it doesn't have the fix for your issue #3, I've read somewhere else about this feature that even the iphone has but not this phone... Good Luck!
Sent from my EVO using xda app-developers app
jocarog said:
Mean bean fixes only your #1 issue...
1.3 AVCRP Bluetooth profile is not available even on a custom kernel, since meanbean uses stock kernel with elemental X over clock modules, it doesn't have the fix for your issue #3, I've read somewhere else about this feature that even the iphone has but not this phone... Good Luck!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I was told CyanogenMod fixed this. Any truth to this claims?
Yea I miss read about the Bluetooth part, my bad Homie
Sent from my EVO using xda premium
Im running cyanogen mod but my car stereo doesn't have that profile so I can't test for you, plus I haven't been able to drive in a month after a surgery... I remember somebody asking thicklizard about this feature in his arc reactor thread and also in the meanbean thread... Maybe you can pm a kernel developer and see what's involved into getting this feature to work on our phones...
Sent from my EVO using xda app-developers app
jocarog said:
Im running cyanogen mod but my car stereo doesn't have that profile so I can't test for you, plus I haven't been able to drive in a month after a surgery... I remember somebody asking thicklizard about this feature in his arc reactor thread and also in the meanbean thread... Maybe you can pm a kernel developer and see what's involved into getting this feature to work on our phones...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Dude I just rooted for the first time ever. I could not begin to tell you who develops kernels to save my life. But I would have to be S-Off for a custom kernel, right? Anybody with Cyanogen Mod wants to chime in on whether AVRCP 1.3 or higher is present?
Holy crap! A google search answered my own question, they claim AVRCP 1.3 was working on Cyanogen Mod 10.0 but that it broke on 10.1. Link here https://jira.cyanogenmod.org/browse/CYAN-20
So, can I just flash 10.0 to my phone? what is the difference between 10.0 and 10.1? are they both jellybean builds?
And another thing, the wife was testing the wifi tether on my phone with her I PAD and connection breaks after about 15 minutes. So it looks like it isnt working after all. I just like turns off by itself. Anybody know why this could be?
darkleafar said:
And another thing, the wife was testing the wifi tether on my phone with her I PAD and connection breaks after about 15 minutes. So it looks like it isnt working after all. I just like turns off by itself. Anybody know why this could be?
Click to expand...
Click to collapse
There is a setting that can be turning it off in the app by itself or it could be the jellybean task killer what rom is she using? And yea you can flash cm 10.0, is jellybean 4.1; cm 10.1 is jellybean 4.2... If you are s-on just remember to extract the boot.img and flash it on fastboot with this command: fastboot flash boot boot.img.
Good Luck!
jocarog said:
There is a setting that can be turning it off in the app by itself or it could be the jellybean task killer what rom is she using? And yea you can flash cm 10.0, is jellybean 4.1; cm 10.1 is jellybean 4.2... If you are s-on just remember to extract the boot.img and flash it on fastboot with this command: fastboot flash boot boot.img.
Good Luck!
Click to expand...
Click to collapse
BUt i was just told if I have RUU 3.16 then i have to downgrade to 3.15 because the 3.16 touchscreen drivers are too new and have not been implemented into the kernel in any AOSP ROMs. correct?
darkleafar said:
BUt i was just told if I have RUU 3.16 then i have to downgrade to 3.15 because the 3.16 touchscreen drivers are too new and have not been implemented into the kernel in any AOSP ROMs. correct?
Click to expand...
Click to collapse
Correct, for that you need to be s-off... Backup all of your stuff and head over to the dirty Racun thread or Facepalm...in the original android development section...