My phone can't connect to my router even though everything is set up correctly and the SSID is on visible. It always says "Not in range. Remembered." ~~
However it can detect my neighbours router ?_? I had this problem on both versions experimental and stable but i can connect normally with any other rom. I really dont want to switch to another rom =/
Here some more infos:
Haykuros "DaNgEr" SPL
Cyanogen recovery 1.4
Cyanogen Rom 4.1.11.1
Running the same rom as you, but not the same spl. Hard spl is installed on mine. No issues what so ever with WiFi. I've never had WiFi issues with Cyanogen's, even with 4.0.4.
Yours is the exception I'd guess, not the rule.
I don't believe the ROM is the source of your problem.
Moved as not development.
As i said it detects Wi-Fi on any other rom also on my original nand backup. ~~
The 3G connection seems weeker too and i constantly get "connection lost please retry" msgs.
FWIW, when I run the same ROM and same SPL as you I don't have any WIFI problems (dlink router). I would try re-installing everything.
Re-Installed everything a couple of times but it still wont work ~~ Guess i have to wait for the next barebone stable lol.
velotown said:
Re-Installed everything a couple of times but it still wont work ~~ Guess i have to wait for the next barebone stable lol.
Click to expand...
Click to collapse
Try MENU... SETTINGS...WIRELESS CONTROLS.......WI-FI SETTINGS....MENU....ADVANCED.....REGULATORY DOMAIN....
Try each setting to see if this helps. I had similar trouble and set to 14 it worked fine.
Good luck
YOU SIR ARE MY HERO!
Thank you very much Didn't knew that wi-fi had advanced settings tytytyty.
I had the exact same issue and just tried extending the regulatory domains...wouldn't have thought it would have made a difference or have any effect but it worked and found my router instantly. No idea why my router wasn't showing up in the first place but there ya go!
My wifi connects just fine, but the web only seems to work for Opera Mini, Facebook etc... but it won't work with Dolphin Browser, or downloads in the market place. The default browser works occasionally.
I can browse the marketplace, but when trying to download, it just says "Downloading..." then "Download Paused".
Everything worked on the stock ROM, and everything works fine when I'm using Cellular data. Any thoughts?
Thanks.
billquinn1 said:
Try MENU... SETTINGS...WIRELESS CONTROLS.......WI-FI SETTINGS....MENU....ADVANCED.....REGULATORY DOMAIN....
Try each setting to see if this helps. I had similar trouble and set to 14 it worked fine.
Good luck
Click to expand...
Click to collapse
Hi, Thank you very much.
I have exactly the same issue, and now it's work on 14.
Cheers,
Thierry
Greetings fellow Galaxyenz,
I have a Galaxy S that worked all ok with JF5 stock ROM, paired with my car for phone audio, using bluetooth. Never had a disconnect...
Then I applied the procedure in order to get the HackEclair ROM 1.0.4 (flashed JM5 through ODIN, then recovery and applied update.zip). After that, i applied OneClickLagFix 2.0.
##EDIT## I'm currently on JM7 + Tayutama rom and it still exists.....
At the end my phone flies like a Concord, and it performs 2200 on Quadrant =)
My only problem right now is that Bluetooth connections to the Car audio, only last for 30 seconds.
I have to completely disable and enable Bluetooth on the phone in order to get the audio working again... for 30 more seconds... =(
Although the phone rocks with this ROM, having no bluetooth system in the car because of this ROM, is a no-go for me.
Thanks for you time. This forum has a great helping initiative.. It's precious, let's keep it
Cheers
Phk
EDIT -- Developed a dirty fix. Works OK for me now!
Just to make this thread complete, i've found the bug is related to some configuration desynchronization between car and mobile.
So android bt stack must be reseted.
I've developed my first app for this, so that i can reset confs with one click
thanks to every1 at XDA, you guys rock =)
http://www.multiupload.com/KI0WJ2RKZB or Check attached!
Cheers,
Phk
Good work! Finaly someone fixing stuff on own. You sir are all class
Sent from my GT-I9000 using Tapatalk
Word!
10cc
miki4242 said:
Word!
10cc
Click to expand...
Click to collapse
Thanks miki
The app is now on the Market, and i've realized that my car picks up the device faster if it has a new name after the fix, so i will implement a random "Android-XXXX" name for each time you click "Fix" =)
Install it from the Market to make sure you receive updates.
I'll also try to perform these steps, as they as what i really to:
- turn off bluetooth
- run this apk
- press fix
- turn on bluetooth
- change name
- reboot
Cheers!
Cool to see you addressing this with your own fix, but JM5 did have buggy BT with my car as well. Never a problem with JM6, JH1 or JM7. Maybe the better fix is to just get one of those firmwares, which don't have the problem you describe, and also drastically improve GPS (really, they do - for me anyways) and also are much less "laggy" even without fixes.
Hey distorted... Sorry to disappoint you, but I have JM7, and yes, the problem is still there That's why i've built up the tool, i have to use it every 2 days (more or less)
Anyway thanks for the thumbs up! =)
Cheers
Phk said:
Hey distorted... Sorry to disappoint you, but I have JM7, and yes, the problem is still there That's why i've built up the tool, i have to use it every 2 days (more or less)
Anyway thanks for the thumbs up! =)
Cheers
Click to expand...
Click to collapse
Disappoint me? LOL, not at all. I don't have the problem since moving on to newer leaked firmwares than JM5. I definitely had the problem on JM5, though.
Perhaps you should rename the thread, then, if it's not specific to JM5.
Additionally, your OP says nothing about different firmwares other than no problem on JF, but the problem on JM5, maybe you should include that the issue is there on JM7 also.
And finally, if you're still running RyanZA's lagfix, and/or the HackEclair ROM, how do you know they're not the real root of your BT problems?
Coincidentally, I was also on OCLF hack and JM5 when I had BT problems. Maybe it's the OCLF that's the problem, since I am on JM7 and don't use OCLF any more, and don't have the problem, but you do(?).
distortedloop said:
Disappoint me? LOL, not at all. I don't have the problem since moving on to newer leaked firmwares than JM5. I definitely had the problem on JM5, though.
Perhaps you should rename the thread, then, if it's not specific to JM5.
Additionally, your OP says nothing about different firmwares other than no problem on JF, but the problem on JM5, maybe you should include that the issue is there on JM7 also.
And finally, if you're still running RyanZA's lagfix, and/or the HackEclair ROM, how do you know they're not the real root of your BT problems?
Coincidentally, I was also on OCLF hack and JM5 when I had BT problems. Maybe it's the OCLF that's the problem, since I am on JM7 and don't use OCLF any more, and don't have the problem, but you do(?).
Click to expand...
Click to collapse
Yes, i might change the thread name
I'm on JM7 now with OCLF, but there's absolutely no reason for OCLF being the root of the problem.. Have you checked the full source code? I've read it line by line...
Phk said:
Yes, i might change the thread name
I'm on JM7 now with OCLF, but there's absolutely no reason for OCLF being the root of the problem.. Have you checked the full source code? I've read it line by line...
Click to expand...
Click to collapse
Full source code? Do you mean the scripts it runs? Of course I have. I manually ran them one by one to install OCLF on my phone since the batch doesn't work on Macs, and I generally want to know what exactly some script is doing to my phone in case I have to undo the steps if the script borks my phone.
Perhaps there's no reason OCLF (or Hackclair) would cause this problem, but lets look at the little bit of known data we have between the two of us:
Me: JM5 + OCLF = buggy BT
Me: JH1 + voodoo = working BT
Me: JM7 + voodoo = working BT
You: JF3 + nothing = working BT
You: JM5 + Hackclair + OCLF = buggy BT
You: JM7 + OCLF (+ Hackclair??) = buggy BT
The only common elements to EVERY scenario that has buggy BT that we have specifics to so far include OCLF.
It seems perfectly reasonable to assume that OCLF (and/or Hackclair if you're running it in your current buggy BT configuration) are part of the problem (edit: unless of course you just have buggy hardware).
With that in mind, a reasonable troubleshooting step would be to uninstall both OCLF and Hacklair and see if you have issues on stock JM7. If you don't, then we know that one of those modifications are the problem.
Since you've found for you what is an acceptable workaround, it's probably more effort than you're interested in doing to test that out, and I'm not interested in breaking what is a perfectly working combination of firmware/lagfix on my phone to install OCLF to test it out, so we'll probably have to rely on others reporting their configurations that work or don't work.
The only technical reason I might suspect OCLF as the issue is that in my experience, and the reports of others I've read, OCLF starts to lag again after a day or two of uptime on the phone. What if the BT disconnects are related to the system lagging? It's a stretch, I know, but I can't ignore the fact that between the two of us, the only thing we had in common while experiencing BT issues is OCLF. That's significant, in my humble opinion.
All that said, if I start experiencing BT problems out of the blue on any future configuration, I'll certainly look to your app for help!
distortedloop said:
Full source code? Do you mean the scripts it runs? Of course I have. I manually ran them one by one to install OCLF on my phone since the batch doesn't work on Macs, and I generally want to know what exactly some script is doing to my phone in case I have to undo the steps if the script borks my phone.
Perhaps there's no reason OCLF (or Hackclair) would cause this problem, but lets look at the little bit of known data we have between the two of us:
Me: JM5 + OCLF = buggy BT
Me: JH1 + voodoo = working BT
Me: JM7 + voodoo = working BT
You: JF3 + nothing = working BT
You: JM5 + Hackclair + OCLF = buggy BT
You: JM7 + OCLF (+ Hackclair??) = buggy BT
The only common elements to EVERY scenario that has buggy BT that we have specifics to so far include OCLF.
It seems perfectly reasonable to assume that OCLF (and/or Hackclair if you're running it in your current buggy BT configuration) are part of the problem (edit: unless of course you just have buggy hardware).
With that in mind, a reasonable troubleshooting step would be to uninstall both OCLF and Hacklair and see if you have issues on stock JM7. If you don't, then we know that one of those modifications are the problem.
Since you've found for you what is an acceptable workaround, it's probably more effort than you're interested in doing to test that out, and I'm not interested in breaking what is a perfectly working combination of firmware/lagfix on my phone to install OCLF to test it out, so we'll probably have to rely on others reporting their configurations that work or don't work.
The only technical reason I might suspect OCLF as the issue is that in my experience, and the reports of others I've read, OCLF starts to lag again after a day or two of uptime on the phone. What if the BT disconnects are related to the system lagging? It's a stretch, I know, but I can't ignore the fact that between the two of us, the only thing we had in common while experiencing BT issues is OCLF. That's significant, in my humble opinion.
All that said, if I start experiencing BT problems out of the blue on any future configuration, I'll certainly look to your app for help!
Click to expand...
Click to collapse
Thanks man Useful post! I've spoken to RyanZa before implementing this app, to confirm that there were no possible misunderstandings.
About the code: I was refering to OCLF source code (GPLv3) of the Market App
About the lag returning: I reboot my mobile frequently so the 2 day lag-reappear is not the question
Anyway, you are right, there is a common name: OCLF.
I might test this BT with Voodoo. What are the downsides of voodoo vs oclf? oclf is very neat and clean you know... ?
Phk said:
Thanks man Useful post! I've spoken to RyanZa before implementing this app, to confirm that there were no possible misunderstandings.
About the code: I was refering to OCLF source code (GPLv3) of the Market App
About the lag returning: I reboot my mobile frequently so the 2 day lag-reappear is not the question
Anyway, you are right, there is a common name: OCLF.
I might test this BT with Voodoo. What are the downsides of voodoo vs oclf? oclf is very neat and clean you know... ?
Click to expand...
Click to collapse
I don't imagine the apk for OCLF does anything different than the scripts do, essentially make the large data file and then loop mount it. So the end result is surely the same.
I don't really want to pollute this thread with the merits of OCLF vs voodoo, some people get a bit to "religious" or defensive about it and the thread will devolve to being really off-topic if that happens. There are plenty of threads hashing that debate out.
Personally, I think voodoo to be nice and clean as well. Voodoo requires a custom kernel and you install it via Odin. It backs up your data, formats /data as ext4, then restores the data it backed up to it. Simple, clean, reliable, but not as simple as just running an app from the Market. (For the record, Ryan, I'm not saying here that your method isn't reliable. )
The primary disadvantage for you to test it out at this point is that the beta1 is no longer available publicly, and the beta2 won't be released until "sometime this week", so really not easy for you to test out.
I am experiencing problems with a Bluetooth car kit as well, but different. Every now and then, the connection hangs. The stereo isn't receiving anything, but displays connection status for phone and media. The Galaxy S displays connection as well, the music player looks like it is working, but no sound can be heard.
When I turn off Bluetooth on my car kit, the Galaxy S still displays connected status. Turning off via status bar shortcut or settings menu makes it stay in "turning off" mode indefinitely. Sometimes I can't even bring down the status bar. And even shutting down the device doesn't work, as it is not completely powered down, I have to force it (10 seconds reset button) anyway. Then boot up and hope it doesn't happen again right away.
I had that problem with JM6 + OCLF and still on JM7 + OCLF, but as far as I can remember, it didn't happen on JF3, where I had OCLF running for quite a while as well. And I use my car kit every working day. I never ran JM6/JM7 without OCLF though, so this may not be related at all.
Getting off topic now, but I noticed something else with OCLF: when it is applied, and I connect the USB cable, it locks the internal and external SD cards even when in menu mode without choosing "mass storage". In that state, I can't access them neither from the PC nor from the phone. I need to select "mass storage" then disable it again (already put it as default because of that), which is also pretty annoying because my car charger does fake a PC connection (probably because some devices won't charge otherwise).
Before OCLF, I could just ignore the popup menu for USB mode. I am just saying that, because it is another side effect of OCLF which can hardly be explained by looking at the source.
PlanetJumble said:
I am experiencing problems with a Bluetooth car kit as well, but different. Every now and then, the connection hangs. The stereo isn't receiving anything, but displays connection status for phone and media. The Galaxy S displays connection as well, the music player looks like it is working, but no sound can be heard.
When I turn off Bluetooth on my car kit, the Galaxy S still displays connected status. Turning off via status bar shortcut or settings menu makes it stay in "turning off" mode indefinitely. Sometimes I can't even bring down the status bar. And even shutting down the device doesn't work, as it is not completely powered down, I have to force it (10 seconds reset button) anyway. Then boot up and hope it doesn't happen again right away.
I had that problem with JM6 + OCLF and still on JM7 + OCLF, but as far as I can remember, it didn't happen on JF3, where I had OCLF running for quite a while as well. And I use my car kit every working day.
Getting off topic now, but I noticed something else with OCLF: when it is applied, and I connect the USB cable, it locks the internal and external SD cards even when in menu mode without choosing "mass storage". In that state, I can't access them neither from the PC nor from the phone. I need to select "mass storage" then disable it again (already put it as default because of that), which is also pretty annoying because my car charger does fake a PC connection (probably because some devices won't charge otherwise).
Before OCLF, I could just ignore the popup menu for USB mode. I am just saying that, because it is another side effect of OCLF which can hardly be explained by looking at the source.
Click to expand...
Click to collapse
Wow, that's a totally uncommon behaviour from SGS!
How do you flash it? Do you use CSC+MODEM+PDA? Re-Partition?
Cheers, good luck!
Phk said:
Do you use CSC+MODEM+PDA? Re-Partition?
Click to expand...
Click to collapse
Yes, on both updates, all in one step.
But the strange USB behaviour was already present with factory firmware JF3 (after OCLF).
BTW: the Bluetooth problem doesn't happen very often, between once and three times a week I'd say.
PlanetJumble said:
BTW: the Bluetooth problem doesn't happen very often, between once and three times a week I'd say.
Click to expand...
Click to collapse
Yes, same as me. I have to use the fixer to restore connectivity... :\
About the USB, change your SGS using warranty....
Phk said:
About the USB, change your SGS using warranty....
Click to expand...
Click to collapse
I don't think so.
BTW: I moved from OCLF over to Voodoo (and to JM8). And it did solve nearly all problems. Bluetooth never crashed since (also didn't in a few days of Voodoo on JM7). Also now USB connection doesn't automatically lock the SD cards anymore.
And I noticed something else: OCLF prevents fonts from being rendered bold on certain web pages like Google Reader. Missed that before but I thought maybe Google removed the bold fonts to save space. I like it better with bold fonts though, glad to have them back.
Ongoing BT and OCLF Issues...?
Not sure if this is relevant, but I'll post anyway just in case it is and it gives someone else a eureka moment.
I'm on a stock Eclair ROM - JM2, I know, I've re-flashed it several times now...! - and have had no end of troubles with some combination of root, OCLF and/or the other XDA kernel mods that come with OCLF. I've ruled out the last of these by not changing scheduling or anything else from defaults; I doubt it's the first of them because I've tried a couple of different root methods. So it's probably OCLF itself, I just don't have the appetite yet to re-install everything only to screw it up again "to see if" ...
Anyway, rSAP carkit - pair, connect, everything is fine. Install OCLF, and within a day or two (and *perhaps* related to having to remove/reinitiate the ext2 partition because of the Kies sync issues), I get:
1. Carkit unable to see the 'phone at all (rare, may be unrelated)
2. Carkit sees, connects, but tells me there's no signal (dashboard shows blank signal bars, RNS510/Columbus head unit tells me there's no network) - but I can still make calls
3. Carkit sees, connects, but tells me there's no signal as above but genuinely means it: any attempt at calling gives a network error (most common)
4. Carkit and 'phone won't disconnect properly, so the 'phone is locked out of the network until you reboot it (rSAP borrows the SIM identity of the 'phone for the car, so if it doesn't give it back then the 'phone can't reconnect to the network - the handset thinks it has no SIM card). (every time)
I'm just rebuilding the handset (again) without any mods to see if the problem goes away, but I can't imagine it's related to any other application that I have installed.
Pity me and my poor, laggy handset.... if I find out more, I'll report back. I might have a look at the BT fix posted here (thanks in advance!) to see if that helps if the problem does reoccur... or try Voodoo, so long as I can do it without my wife spotting that I'm in the process of breaking that very expensive 'phone again
I recently got the lg optimus x2. It is running on 2.3.4.
Initially, the wifi connected but 3g was not recognised even though data roaming and access was enabled. However, now i cannot even connect to wifi. It keeps saying 'obtaining ip add' and then fails.
Going through various google searches I have messed around with the settings, set apn to default. Done factory reset. Disconnected, reconnected, changed sim cards, tried 2g, messed around with vpn, selected all network mode's but nothing seems to work. I have contemplated rooting the phone but doubt this will do anything?
This is extremely frustrating considering the "amazing" reviews the phone has one expects a simple tool such as wireless connection to work.
Would be grateful if anybody had any other ways to possibly resolve the issue?????
Thanks
dental7 said:
I recently got the lg optimus x2. It is running on 2.3.4.
Initially, the wifi connected but 3g was not recognised even though data roaming and access was enabled. However, now i cannot even connect to wifi. It keeps saying 'obtaining ip add' and then fails.
Going through various google searches I have messed around with the settings, set apn to default. Done factory reset. Disconnected, reconnected, changed sim cards, tried 2g, messed around with vpn, selected all network mode's but nothing seems to work. I have contemplated rooting the phone but doubt this will do anything?
This is extremely frustrating considering the "amazing" reviews the phone has one expects a simple tool such as wireless connection to work.
Would be grateful if anybody had any other ways to possibly resolve the issue?????
Thanks
Click to expand...
Click to collapse
You should use NVflash to have a "clean" install.
Sent from my LG-P990 using xda app-developers app
tonyp said:
You should use NVflash to have a "clean" install.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
ok i cant do that because i have a mac
is that the only way out?
dental7 said:
is that the only way out?
Click to expand...
Click to collapse
Did you put the right password in for the router?(;
sent from my wii remote
I have heard that this phone only supports some Wi-Fi channels.
Try to change your Wi-Fi channel to 6, for example.
Sent from my Optimus 2X using xda app-developers app
okay, the 3g is now working (although very slow)
I have gone through all the channel lists but no connection still? also, tried open source network but nothing happened???
edye, mpurch
Supupa said:
Did you put the right password in for the router?(;
sent from my wii remote
Click to expand...
Click to collapse
yes, i did....the wifi worked for the first two days when i got the phone but then stopped working.....
ok give up....waste of money and time
gonna throw it out of the window
There are two things you could do ...
1. Return the LG 2X - if that's still possible
2. Switch to a Custom ROM
Installing the first official LG update to my phone was a major setback for me as a lot of things stopped working, that worked before. But switching to a Custom ROM made me a happy man.
Have you considered trying out e.g. DjangoManouche (2.3.x) it is based on the stock ROM but has massive improvements built in.
http://forum.xda-developers.com/showthread.php?t=1410662
If you feel like you want the ICS experience there is NovaHD (based on CM9)
http://forum.xda-developers.com/showthread.php?t=1508492
The only glitch with CM9 is, that there are currently no drivers for the Tegra2 chipset released which results in lack of FullHD video recording, beside that the ROM works like a charm.
I am running NovaHD on my 2x now and not willing to go back to Gingerbread ;-)
If there is anything I can help you with, just let me know!
Cheers!
borgond said:
There are two things you could do ...
1. Return the LG 2X - if that's still possible
2. Switch to a Custom ROM
Installing the first official LG update to my phone was a major setback for me as a lot of things stopped working, that worked before. But switching to a Custom ROM made me a happy man.
Have you considered trying out e.g. DjangoManouche (2.3.x) it is based on the stock ROM but has massive improvements built in.
http://forum.xda-developers.com/showthread.php?t=1410662
If you feel like you want the ICS experience there is NovaHD (based on CM9)
http://forum.xda-developers.com/showthread.php?t=1508492
The only glitch with CM9 is, that there are currently no drivers for the Tegra2 chipset released which results in lack of FullHD video recording, beside that the ROM works like a charm.
I am running NovaHD on my 2x now and not willing to go back to Gingerbread ;-)
If there is anything I can help you with, just let me know!
Cheers!
Click to expand...
Click to collapse
I cant download clockworld mode...so i tried to do it through the computer...and now the phone wont switch on
Hi,
that doesn't sound too good - did you follow any instructions installing clockworkmod?
I installed it using RomManager on the phone itself, worked like a charm.
Did you root your phone already?
I couldn't install it directly as i had no 3g/wifi (initial issue)...after i transferred the Nova Hd file into the SD, installed clockworld through PC and attempted a restart it wouldnt switch back on
Have you tried removing the battery and inserting it again? - Did you turn on the phone while pressing volume down (until the first LG logo disappears)?
This should then boot into clockwork recovery if you installed it correctly before.
borgond said:
Have you tried removing the battery and inserting it again? - Did you turn on the phone while pressing volume down (until the first LG logo disappears)?
This should then boot into clockwork recovery if you installed it correctly before.
Click to expand...
Click to collapse
done both, nothing works- phone is dead as a brick
This might be a dumb question, but has the battery still power? Have you tried with the power cord attached?
Is there nothing on the screen, no lights blinking? Brick dead?
Does this sound similar?
http://forum.xda-developers.com/showthread.php?p=28050395
borgond said:
This might be a dumb question, but has the battery still power? Have you tried with the power cord attached?
Is there nothing on the screen, no lights blinking? Brick dead?
Does this sound similar?
http://forum.xda-developers.com/showthread.php?p=28050395
Click to expand...
Click to collapse
yes it does....yes i attached it to my computer...nothing happened
no lights, nothing
I am really sorry that you encountered these severe problems :-(
Did charging at the wall or just running off wall power do anything?
This might be late, but here are some topics that could be of help:
http://forum.xda-developers.com/showthread.php?t=1037751
http://www.knowyourcell.com/lg/lg-g2x/g2x-guides/835561/how_to_hard_reset_the_lg_g2x.html
This one is in german, but using chrome it shouldn't be a problem to translate:
http://www.handy-faq.de/forum/lg_op...d_p990_clockworkmod_recovery.html#post1884465
All the best!
Maybe this might help as well?
http://forum.xda-developers.com/showthread.php?p=28110661
borgond said:
Maybe this might help as well?
http://forum.xda-developers.com/showthread.php?p=28110661
Click to expand...
Click to collapse
No, none of those links aided the matter- but thanks anyway.
guess im done and dusted with this phone. what a waste of money and time.
time for a iphone i guess
Last night I updated to Euro v20a and sadly I am unable to make my sixaxis controller app to work on it, I am having following 2 issues:
1. "Sixaxis controller checker" giving error like - Could not start driver. Check that the driver has been given permission to run by the superuser app.
2. Also everytime after opening this app my bluetooth stops to work? I have tried to share file but it always fails then I have to restart the phone to share anything via bluetooth.
In v10e I had no problem with this app except that everytime after using it my Wifi gets closed then I had to restart phone but now after upgrade to 20a its not working at all.
My phone is rooted and all other app seems to work fine.
Anyone facing similar issue? Please share?
shazmekool said:
Last night I updated to Euro v20a and sadly I am unable to make my sixaxis controller app to work on it, I am having following 2 issues:
1. "Sixaxis controller checker" giving error like - Could not start driver. Check that the driver has been given permission to run by the superuser app.
2. Also everytime after opening this app my bluetooth stops to work? I have tried to share file but it always fails then I have to restart the phone to share anything via bluetooth.
In v10e I had no problem with this app except that everytime after using it my Wifi gets closed then I had to restart phone but now after upgrade to 20a its not working at all.
My phone is rooted and all other app seems to work fine.
Anyone facing similar issue? Please share?
Click to expand...
Click to collapse
I understand that some ROMS do not include some of the bluetooth protocols that this app needs. Cyanogenmod does include these by default (and it seems the current LG ROMs do as well). A version of CM for our phone should be coming out soon after the update comes out, or perhaps LG has added this to the latest 20A version.
AW: Issue using Sixaxis controller app
You should always keep in mind that it's just a leak, nothing official and I just think most of the issues we have now will be gone at the official release...
And if not, some Custom ROM's like CM will solve this issue, as it's already said above this post...
...sent with my LG Optimus 4X HD...
Thanks guys!
I already rolled back to ICS, I know JB is still in testing phase and its far from perfect though interface seems so much better.
I was having 1 issue even in ICS that everytime after using Sixaxis controller app my "Wifi" stops to work and to get it back to work I had to restart my phone infact this issue was the reason I switched to JB where I was not even able to use it at all :crying:
Anyway I am back to ICS and I dont mind restarting the phone at least its working.
shazmekool said:
I was having 1 issue even in ICS that everytime after using Sixaxis controller app my "Wifi" stops to work and to get it back to work I had to restart my phone infact this issue was the reason I switched to JB where I was not even able to use it at all :crying:
Click to expand...
Click to collapse
I have the same issue in ICS. At least Wifi continues to work while the app is still running!
Wenque said:
I have the same issue in ICS. At least Wifi continues to work while the app is still running!
Click to expand...
Click to collapse
Have emailed the issue to developer? After all we have paid for the app so we can request for fix also it will only help them to improve there app.
I have emailed but still no fix. Please email them.
I have USB/BT app but again there is no way to pair my BT PS3 controller without USB connection which is not possible in our device.
This worked for me!!
had the same problem... so i thought maybe with an earlier version it might work...
try with 0.5.7 that's the one that worked for me!!
Do you think there will be a new version which fix 20A compatibility ?
DirtyShady said:
Do you think there will be a new version which fix 20A compatibility ?
Click to expand...
Click to collapse
new versions came out a few days ago 0.6.3 and 0.6.4 supposed to resolve some compatibility issues. I already tried them both but still the same problem so i'm still using 0.5.7 in V20a.
not working for me either
chorchi said:
new versions came out a few days ago 0.6.3 and 0.6.4 supposed to resolve some compatibility issues. I already tried them both but still the same problem so i'm still using 0.5.7 in V20a.
Click to expand...
Click to collapse
i have tried your suggestion of installing an older version, starting with 0.5.7 as stated, and after having no luck any older version i could find/download.
this app is still not working on my 4x V20a hopefully they will hear our pleas (i have also contacted them to let them know of the compatibility issue) and update the app with compatibility. but if someone manages to sort this out before they do... PLEASE LET ME KNOW!
strange thing is that the compatibility checker still works for me (registering my button presses after connecting, etc...)
fingers crossed + thanx in advance for any help.
chorchi said:
new versions came out a few days ago 0.6.3 and 0.6.4 supposed to resolve some compatibility issues. I already tried them both but still the same problem so i'm still using 0.5.7 in V20a.
Click to expand...
Click to collapse
I just upgraded to v20b Europe Open, and it broke SixAxis.
I'd love to be able to use SixAxis 0.5.7, but don't have a backup of it. I am a legitimate user of the app - I bought it full price from the Play Store. Any advice on where I can get a legit copy of 0.5.7 from?