[q] tvout+wiimote? - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi all,
I know this is at the back of lots of gamers mind's who are using an i9000.
I am running a Darky Rom so I still get TV out - which is a big thing for me.
I got rid of my HD2 for this i9000 - and I still have not been able to connect a Wiimote to my device.
I was playing FPSCE with the wiimote on the HD2 and I really really miss this functionality.
I am aware that the bluetooth Kernal is the issue and that the Cynogen mod roms and others based around this are running a different BT imp which addresses and resolves this issue, but if I jump to Cynogen, I loose my TV out which is sadly more important (blame Ttorrent).
Has anyone heard of anything happening anywhere that will let me play with my wiimote whilst TvOUTed?
I am not holding my breath
Many thanks

Related

Has anyone tweeked bluetooth

I am wondering if there has been any improvements to bluetooth on any of the roms out there. I know there has been some threads regarding the issues with bluetooth since 2.1 and I personally am having issues with my phone staying synced to my car (worked perfect in 1.5). Also does anyone know if froyo get an update to address bluetooth bugs? Thanks.
Bluetooth in 2.1 has been hit or miss depending on the brand you are trying to attach to. I have bluetooth on my computer and can use it fine with my phone. Audio works fine and it stays connected. It could be because I have froyo. IDK.
BTW-This should be in Q&A
BlueTooth does seem to be a little less picky in FroYo.
Hummm maybe its time to try froyo and see if it fixes my issues
Sent from my HERO using XDA App

[Q] Developers and BT

Which features of a ROM Kernel or Modem have the most influence on BT function. I recently purchased a Kenwood X994 for the car and the Captivate seems to have to be "connected" every time. Sometimes it loads the phone book, other times not. I have never been asked for a PIN code when pairing. Even after flashing a new ROM and reinitialization the Kenwood. It does work but even with th Gamin BT the connections were automatic.
I think the Developers might have an idea what influences the BT stack and if any ROM/Kernel/Modem is better in that regard.
If this post is in the wrong area please move it.
bump - I have the same concerns. Can't seem to find consistent bluetooth connection that was better than stock with lots of trying different roms with different modems and am totally confused on what directly affects the bluetooth connection
tbong777 said:
Which features of a ROM Kernel or Modem have the most influence on BT function. I recently purchased a Kenwood X994 for the car and the Captivate seems to have to be "connected" every time. Sometimes it loads the phone book, other times not. I have never been asked for a PIN code when pairing. Even after flashing a new ROM and reinitialization the Kenwood. It does work but even with th Gamin BT the connections were automatic.
I think the Developers might have an idea what influences the BT stack and if any ROM/Kernel/Modem is better in that regard.
If this post is in the wrong area please move it.
Click to expand...
Click to collapse
I am not trying to sell my ROM to you as I don't and am not here to make any money but I have not found a device that Phoenix Ultimate can not connect to. Just a thought for you.
Unless your making your own kernel thats special , their is some devices that it will have trouble connecting to, specifically certain car Bluetooth sets. this was a problem with every kernel I tried, and other users reported this also. I don't think it has anything to do at all with the Rom anyway,(it could, I didnt look into it too much), it think its an issue with kernels built from I9000 source.
adamholden85 said:
I am not trying to sell my ROM to you as I don't and am not here to make any money but I have not found a device that Phoenix Ultimate can not connect to. Just a thought for you.
Click to expand...
Click to collapse
Adam I have used (and am currenty trying out Phoenix Ultimate) and really find you ROMS useful, The BT works fine but the issue is I have to "connect" the phone even though it has been paired
The Kenwood X994 uses Parrot BT system which is supposed to be the best (which is why I chose the Kenwood LOL), I am just wondering why the device cannot auto connect when I get in the car as it did with the Garmin and the Honda. IS there a task I can set up using task manager?
Maybe its the Kenwood. But searches in that arena show no ill effect except with the Captivate and some Droids. IPhone is flawlwess with that system (wouldn't you know it) as are HTC phones it appears. I really hate having to select a phone based on BT in the car.
di11igaf said:
Unless your making your own kernel thats special , their is some devices that it will have trouble connecting to, specifically certain car Bluetooth sets. this was a problem with every kernel I tried, and other users reported this also. I don't think it has anything to do at all with the Rom anyway,(it could, I didnt look into it too much), it think its an issue with kernels built from I9000 source.
Click to expand...
Click to collapse
Which I thought as well so I flashed Cognition 4.2 and had the same issue...and decided to try Phoenix (GPS was terrible on Cog) Well I guess until I get another phone brand I will have to just make sure I connect the already paired devices. Although iPhone doesn't interest me...maybe HTC,
Moved as not android development

Bluetooth Auto Connect

Hi,
I bought a Bluetooth Car Stereo. I've paired it and it pairs fine. When I connect it, it works great and IF I leave BT permanently on, it automatically connects when I sit in the car. If I disable bluetooth to conserve battery, upon re-enabling it, it DOES NOT automatically connect. Instead, I have to go Settings, Wireless, Bluetooth and press Connect manually.
Is there no way of making my phone automatically scan or check or whatever? I'm pretty sure my old Nokia could connect automatically, in fact I'll test now!
Thanks,
Joe
Anyone? Perhaps an app you can recommend?
Bluetooth Autoconnect (by WestOneTech) ... but it's not free ...
Okay. I flashed MIUI MintBerry Edition, and guess what? It allows automatic reconnecting on bluetooth enable. So I know for a fact this isn't some android limitation and it's definitely a setting or config of some sort in SGS firmware.
There has to be a way in which this can be fixed on a stock rooted ROM.
Any help would be smashing!
That happens to me with my samsung gt-s5560 witch is a rather crappy phone. I need to manually tell the phone to connect with my car, even if it's paired and set to auto permit.
On my SGS with ICS EliteRom 1.2, however, it works perfectly. Connects automatically whenever i have bluetooth on (either if it was on before being in range or if i connect while i'm in range).
Bluetooth works as handsfree for calls - from the car interface the phone allows to take and place calls, browse through recent and lost calls, phonebook (it even downloads it) and it even streams music to my car's speakers (using Google Music) with no additional configs.
It connects rather fast, like 3 or 4 seconds after turning BT on.
Exactly Kayn and that is why I can't understand why the stock room doesn't do this and more to the point why nobody has raised this issue before. I like the stock ROM. I genuinely do. I find it intuitive. So why can't it automatically connect to my car stereo when Bluetooth is switched on. This custom ROM has no problem doing it. I simply switch on Bluetooth and boom it connects. I need that functionality on the stock ROM if possible
Im going to flash the newest value pack tomorrow and see if that helps but I doubt it will. I genuinely believe this is an issue with the stock ROM. The only thing that might have caused it if the stock ROM does support it, is if I've removed something using TiBa but I very much doubt it. I didn't touch any core system components.
Haven't flashed the latest value pack but I've worked out how to make it work. Ridiculous on Samsungs part and I think they need to get their heads out of their arses and sort it.
If I activate Bluetooth before I turn on my car stereo, then it picks it up perfectly.
So if I turn on my car stereo and then switch on bluetooth... doesn't work.
If I turn on bluetooth then switch on my car stereo... works fine.
Absolute joke on Samsungs part that this glitch is the only way I can get it to work. I'll keep investigating and I'll eventually write a guide to help people with it.
skezza said:
Haven't flashed the latest value pack but I've worked out how to make it work. Ridiculous on Samsungs part and I think they need to get their heads out of their arses and sort it.
If I activate Bluetooth before I turn on my car stereo, then it picks it up perfectly.
So if I turn on my car stereo and then switch on bluetooth... doesn't work.
If I turn on bluetooth then switch on my car stereo... works fine.
Absolute joke on Samsungs part that this glitch is the only way I can get it to work. I'll keep investigating and I'll eventually write a guide to help people with it.
Click to expand...
Click to collapse
Makes us both but i can't really cope with the battery drainage when the phone's plugged during several hours (i use loads of battery intensive like torrent-downloading apps, radio streaming, etc and the phone needs to be plugged) so i had to make the change for some custom non-samsung based rom.
Samsung has loads of this minor quirks that make the experience that much less enjoyable. I only found solution in custom roms (very thankful to the devs for that!). Don't think they ever really cared about solving some under-the-hood issues (they did add some new features though) and even went as far as to pull the "flawed by design" apple-move.
I would still tell you to give a shot at customs, some out there are really good, but i can understand not wanting to change something we really like.
Good luck with that mate!
It's not that I don't like custom ROMs, I love custom ROMs but unfortunately, none of them have the Samsung Browser and let's be honest, everyone knows the best Android browser is the stock Samsung one. The browser that came with MIUI was very choppy and laggy.
I get decent battery life out of my stock ROM, but if I had to leave BT on permanently this would go down a lot! I suppose i just need to remember that as I get into my car, turn on BT and it'll connect first time.
Just crap that other Custom ROMs can search on enable and connect. Worst still, I can't believe we're the only ones who have this issue.
I never thought samsung browser was something that good, i hardly even see it being mentioned. I never really used it much since i have not used sammy's roms since ginger bread came out, but have you tried opera mobile? This is, by far, the best browser I've used, it's not even fair to compare - it's on a totally different league. I was actually losing hope of decent browsing (tried just about anything) on Android until i came across opera. Needs to be the mobile and not the mini. Faith in Android browsing restored
if you haven't, give it a shot, free on market. If that's the main reason not to use a custom rom, you may be changing your mind soon
Sent from my GT-I9000 using xda premium
I am having just the opposite issue, I have a bluetooth headset that auto connects every time it's in range if I want it to or not, I'm running a stock rooted room kitkat on an old Nexus 7

Sixaxis Controller

Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
DBak451 said:
Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
Click to expand...
Click to collapse
I've got it to work, will try it on lollipop.

[Q] Anyone having issues with Moga controller?

I'm using a rooted N6, stock ROM but with the Franco Kernel and I'm having trouble getting my Moga Power Hero controller to work. It connects fine, but none of the games work with it that are supposed to. I tried Ravensword, Riptide, and RiptideGP2. Nothing... not even in HID mode. HID mode DOES work in Leo's revenge and on a couple of other things... Could there be some sort of Android 5.0 controller compatibility issue going on or might it be the kernel?
I contacted Moga, they said to take it up with the game devs - no support. I get that, but not even a word of general issues with Android 5.0. I contacted the dev of Ravensword a few days ago inquiring about it, but so far no word on the issue either.
Anyone else having an issue?

Categories

Resources