Related
Hi,
I have tried the official roms, villainrom 12 (excellent!) and cronos 2.1.3 (also excellent!). All have the horrible bluetooth problem of skips in the music, then a speed up/slow down that results in pitch changes.
I saw that Darchdroid got it fixed in the CDMA version and wondered if there are any roms for the GSM version that have it fixed too? Just in case I missed it!
Thanks
nobody in this forum seems to know how to fix it. I've asked but nobody knows, i believe the only sense rom that i never had the skipping was behnaam's legend port.
I am not experiencing this with VillainROM 12. Didn't have it with CyanogenMOD by Elemag either...
none of the Aosp based roms have this problem it seems to be only sense related. I've had this problem with villain,cronos,chocolateeclair,etc and nobody had any idea when i asked the same question. I actually am going to try to move the bluetooth firmware and files from the legend rom i mentioned above into another newer sense rom I just have to read up on resigning the zip, I'm a super noob to all that is linux.
Moved to Q&A as not development. Temporary redirect put in place.
ggrammer said:
nobody in this forum seems to know how to fix it. I've asked but nobody knows, i believe the only sense rom that i never had the skipping was behnaam's legend port.
Click to expand...
Click to collapse
Thanks, although I have also tried Cronos 2.2 (Froyo) that doesn't have sense and it still did the pitch/speed change.
kosmiq said:
I am not experiencing this with VillainROM 12. Didn't have it with CyanogenMOD by Elemag either...
Click to expand...
Click to collapse
Can I ask what car head unit or bluetooth headset you were using? It definitely does it with my Sony BT2600 car unit and both Cronos & Villainrom.
ggrammer said:
none of the Aosp based roms have this problem it seems to be only sense related. I've had this problem with villain,cronos,chocolateeclair,etc and nobody had any idea when i asked the same question. I actually am going to try to move the bluetooth firmware and files from the legend rom i mentioned above into another newer sense rom I just have to read up on resigning the zip, I'm a super noob to all that is linux.
Click to expand...
Click to collapse
Could you let me know an AOSP rom to try that you know it works in please? - although I really like sense, I hate this issue and could live without it to get it fixed.
I'm pretty much a noob at this too but I'll help as much as I can!
like kosmiq mentioned Elemag's CMH rom doesn't seem to have this issue (I've used this rom alot and I have a 2010 Mazda3 and the bluetooth in the mazda is wonky at best and this rom works perfectly with it). As far as cronos froyo I haven't tried the bluetooth in that yet in my car but that is still an alpha development so if you need something more stable and complete then stay away from it, It is a great rom and the one I am running now but I am probably going to flash over to Maxisma's newest legend+WWE combo rom.
Good to see Maxisma back.
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
First, I am currently s-off and running NeoMax v2.0 with what I believe are the newest firmware and radios. I also have Sebastian's overclock kernel. While reading the AOKP-Neo thread, I noticed that it doesn't support custom kernals. Will I be okay just doing a wipe and flashing the Rom, or do I need to do something else because of the kernel I'm currently running?
Next, I understand that there are some bluetooth issues with voice and audio, but does anyone know of any problems when connecting peripherals such as bt keyboards or game controllers? I should be receiving the new Nyko Gamepad soon and am anxious to try it out.
Lastly, I know that It's been previously discussed but I haven't seen an answer that satisfies my needs yet. The AOKP camera qualitly is just plain lousy. I understand that the sense camera is incompatible because it is based on sense. Is it the sense firmware that makes the sense camera so great, or is it the program itself? Would it be difficult to reverse-engineer the program to run on AOKP? Admittedly, if It's not already obvious, I know next to nothing about writing programs and give major props to all the devs here, but is anyone working on this, or should I stop holding my breath?
aftafoya said:
First, I am currently s-off and running NeoMax v2.0 with what I believe are the newest firmware and radios. I also have Sebastian's overclock kernel. While reading the AOKP-Neo thread, I noticed that it doesn't support custom kernals. Will I be okay just doing a wipe and flashing the Rom, or do I need to do something else because of the kernel I'm currently running?
Next, I understand that there are some bluetooth issues with voice and audio, but does anyone know of any problems when connecting peripherals such as bt keyboards or game controllers? I should be receiving the new Nyko Gamepad soon and am anxious to try it out.
Lastly, I know that It's been previously discussed but I haven't seen an answer that satisfies my needs yet. The AOKP camera qualitly is just plain lousy. I understand that the sense camera is incompatible because it is based on sense. Is it the sense firmware that makes the sense camera so great, or is it the program itself? Would it be difficult to reverse-engineer the program to run on AOKP? Admittedly, if It's not already obvious, I know next to nothing about writing programs and give major props to all the devs here, but is anyone working on this, or should I stop holding my breath?
Click to expand...
Click to collapse
1. I believe that since you are s-off you can simply flash through recovery and the kernel will install itself. If not you can always do what s-on people like myself do and flash the boot.img through fastboot before booting into the rom for the first time.
2. Not sure.
3. From what I have heard the Devs talk about or how they react, it is not possible to run the sense camera on AOSP or AOKP roms since the app runs on the sense framework that is obviously absent in AOSP or AOKP. From what I understand there is no way to get the sense camera to work without the framework, and I am assuming the Devs that have the knowledge to work around something like that are busy with other, larger issues.
hope this helps
You should be fine just flashing things through the recovery, since Sense and AOSP roms use different kernels it should overwrite it. If you want to be completely sure nothing screws up you can always wipe the boot partition if you are using the latest version of TWRP.
aftafoya said:
First, I am currently s-off and running NeoMax v2.0 with what I believe are the newest firmware and radios. I also have Sebastian's overclock kernel. While reading the AOKP-Neo thread, I noticed that it doesn't support custom kernals. Will I be okay just doing a wipe and flashing the Rom, or do I need to do something else because of the kernel I'm currently running?
Next, I understand that there are some bluetooth issues with voice and audio, but does anyone know of any problems when connecting peripherals such as bt keyboards or game controllers? I should be receiving the new Nyko Gamepad soon and am anxious to try it out.
Lastly, I know that It's been previously discussed but I haven't seen an answer that satisfies my needs yet. The AOKP camera qualitly is just plain lousy. I understand that the sense camera is incompatible because it is based on sense. Is it the sense firmware that makes the sense camera so great, or is it the program itself? Would it be difficult to reverse-engineer the program to run on AOKP? Admittedly, if It's not already obvious, I know next to nothing about writing programs and give major props to all the devs here, but is anyone working on this, or should I stop holding my breath?
Click to expand...
Click to collapse
if you flash AOKP and have s-off you will get a custom kernel installed. There are a couple of kernels for AOSP right now. Snuzzo has the most customized one for AOSP
only BT issue that is left is BT calling
camera quality is the same from aosp to sense. only difference is sense cam can do 1080p video recording and aosp can only do 720p
Hi guys... I'm trying to solve a problem with my Vibrant, CM10 works except it doesn't give me data connection. But first I have to tell you a bit of a backstory
So, a couple of months ago I was a Vibrant CM9 user, never been able to solve the data problem with CM10 so I stick w/ 9. Then I decided to sell my phone and I put up an annuncment saying the phone has this and that and that and it comes with ICS.
Then CM9 for Vibrant disappeared from CM site (never understood why) and I couldn't sell my device with a ROM that was not supported anymore. I found a buyer and told him that actually I wasn't able to give him the phone w/ ICS and he was fine with it, so I sold the phone.
Now he just called me and said that the CM7 was draining is battery in 4h (never happened to me) and so he had someone installing another ICS custom ROM (he doesn't know which one) but it is buggy and bla bla bla and he asked for my help.
I don't want to ignore him, I was the one who kinda dropped the ball in the first place not giving him what I promised, and the easiest, quickest and better way to help him would be to having him install CM10 and solve the data connection thing. Another easy way would be to get a CM9 zip, but there must have been a reason for them to remove it... right?
Why all the story? To tell you that now I have to fix a problem on a device that I don't have with me
Now I explained everything to him and instructed him to install CM10, and I'm waiting to hear back from him.
I live in Italy and I have a minor carrier, he has one of the big ones... I was hoping that that alone could solve the problem, but most likely it doesn't matter at all.
Any suggestions?
Thank you a lot in advance.
Flashing any Jelly Bean ROM on one of the Vibrants I have with no SIM card installed will yield no cell data when the card is put back in.
Flash the same ROM with the SIM card in and cell data comes up perfect.
If you're flashing with the SIM card out it might be worth trying with it back in...
The other Vibrant I have doesn't care at all if the card is in or out.
Thank you for your help, I don't believe this applies to the Vibrant that I had, but I'll remember it and I'll try to put the sim in and out or something. The guy didn't reply to me yet... we'll see.
In the mean time any other thoughts are welcome
CM7 should NOT be used. Ideally you should run CM10 or CM10.1 to make sure you have the best E911 experience.
Has he tried flashing CM10 maybe it'll work with his SIM card or however he does it.
FaultException said:
CM7 should NOT be used.
Click to expand...
Click to collapse
Did you mean CM9? Because of the EU Bug? Or what is wrong with CM7?
Anyway E911 is not important because in Europe the universal emergency number is that uses the E911 system is 112, but here in Italy we are retarded and we didn't implemented it yet. Seems like it's a work-in-progress thing, but it's complicated because in Italy 112 has always been another emergency number (carabinieri answer to it)... and also because we are retarded.
Marlon90 said:
Did you mean CM9? Because of the EU Bug? Or what is wrong with CM7?
Anyway E911 is not important because in Europe the universal emergency number is that uses the E911 system is 112, but here in Italy we are retarded and we didn't implemented it yet. Seems like it's a work-in-progress thing, but it's complicated because in Italy 112 has always been another emergency number (carabinieri answer to it)... and also because we are retarded.
Click to expand...
Click to collapse
CM7 and probably part of CM9 had intermittent issues so latest CM10 is best.
same here
FaultException said:
CM7 and probably part of CM9 had intermittent issues so latest CM10 is best.
Click to expand...
Click to collapse
I used for a while the CM9 on sensation xe and had no issues with data connection. After moving to the CM10 (CM version= 10-20130119-EXPERIMENTAL-pyramid) I'm now having that problem. The WIFI works great but no data connection on the mobile network. I tried rebooting, wiping cach/dalvik cach, reset network to default settings...nothing worked for me.
any help!
I love the CM 10.1 build of 4.2.2. It is my dream phone right now. The problem is that no WIFI tethering works on it as of yet. If anyone has anything working I'd love to be proven wrong. This is a show-stopper for me. I can't use bluetooth because my laptop doesn't have bluetooth.
I tried every tethering app out there. Barnacle was the best in that it reported the errors it was seeing instead of just refusing to work.
Anyway, I am thinking of working around the problem by keeping a ROM stored as a TWRP backup that I can restore when I need tethering. I don't need tethering on a moment's notice.
I would like the tethering ROM as slim as possible. I haven't tried any yet. Would a restore be any faster with a slim ROM?
Can someone suggest what ROM I should use that has a small footprint and can restore quickly? I'm thinking that I won't have any apps and no account logged in. If I'm tethering I will be using the other device for email etc. And I'm sure the phone will work no matter what I'm running.
Can anyone suggest a better workaround than this?
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
crutzulee said:
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
Click to expand...
Click to collapse
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
mchahn said:
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
Click to expand...
Click to collapse
Sounds like a bad download...Did you download straight to your phone? While I've never had this issue, I have heard that some prefer to download to their computers and transfer the zip to their phones..
You might be right. I did download it to my PC and copy over the zip. However, I had trouble copying and I had to copy a second time. So, I'll try again.
I did a fresh download, copied, wiped, flashed, and it didn't work. Apparently bam won't run on my phone.
...and your using the latest version of twrp?
Yes. I checked. I might be doing something wrong but I doubt it. I'm guessing there is a bug somewhere that rarely shows up. Until the source code is available these custom roms are somewhat a shot in the dark.
I'm just going to go back to my ICS backup when i need tethering. I guess I started this thread with the hope that someone would have a workaround. I really like 4.2.2 and I've decided to live with this. Maybe it will be fixed soon?
Thanks for your help.
The only tethering app that seems to work is "Open Garden." It's in the Play Store but you'll have to side-load it if on AT&T.
Sent from my SAMSUNG-SGH-I717 using xda premium
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
How do you keep AT&T from seeing that you're tethering?
knoshann said:
How do you keep AT&T from seeing that you're tethering?
Click to expand...
Click to collapse
I don't know who you are replying to, but I tethered all the time with ATT when using ICS. I didn't know they were trying to block it.
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
knoshann said:
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
Click to expand...
Click to collapse
I know that Verizon has folded tethering into the normal data plans. They make it sound like a benefit but they're raising the overall price so they are really forcing you to buy tethering. I thought ATT and the others were going the same way.
I assume they realized they couldn't enforce it any other way.
mchahn said:
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
Click to expand...
Click to collapse
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
chp said:
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I've been to their home page a million times because everyone said you could get the apk there. I was going crazy because all I ever saw was a big orange button to download a version for windows. I had just now typed a reply to you that said you were crazy and then it hit me. You meant to go there on the phone! I'd only been there from my laptop.
Thanks, I'll give it a try now.
-- later --
As I feared, open garden is bluetooth only.
I was researching the hotspot issue that only a few users have been having and found that it is inherent to android 4.1.2 and newer. What I found out:
"Throughout the previous iterations of Android (<4.1.2), Android has not identified for the carriers which data is for tethering, and which is not.
Android 4.1.2 introduced that ability (and requirement) for Android devices to properly flag when data is for tethering purposes. This is the first time this has been used in a vanilla release of Android...
For everyone frustrated by this update to Android: Android respecting a carrier's request to know if data is for a tethered device IS NOT A BUG. IT IS A FEATURE. It's not a feature for users like you and me, it's a feature for manufacturers like Samsung and HTC, so they can in turn build devices that carriers can have more control over.
So, to be clear, THIS IS NOT A BUG. Google INTENDED to respect carrier tethering rules. The only way to circumvent this is to either get a plan from your carrier that allows tethering, revert to a build of Android of 4.1.1 or earlier (I used wugfresh NRT tools, google it, they're amazing and simple: FOR NEXUS DEVICES ONLY, SORRY), or for a developer to find and KILL THE ****ING ABILITY FOR ANDROID TO TAG DATA AS TETHERING DATA and release that to the public; either by providing an modded Android image, or as an app (much less likely to work unless you're rooted)."
Copied from a past on another forum, and apparently I can't post a link to it.
Even though I clicked on Thanks, I'd like to thank you again for that clear explanation. I'm sure it won't take long for that to be hacked.
i think the next nightly may fix it
Next to fix on next Nightly
msm8660: Add Wi-Fi AP module args (i wonder if this is it?)
rkpsym ftewed
I sent JamieD a message about it a few days ago. I'm not sure if all developers were aware with source of the problem. Its especially hard when only some users report having an issue. Hopefully they get it working soon.