PS3 [Problem] Controller loses pairing/sync when used to boot console.

[auracle2g]

Hello guys,

Whenever I use my OEM Wireless Dualshock 3 Sixaxis to wirelessly boot my PS3 up with the PS Button, the controller unsyncs and has to be plugged back into the console to regain sync/pairing. I've tested every other scenario and it is specifically this problem as the only way this happens. Can reproduce it everytime, never witnessed any other way.

So I'm stuck, I don't know what's up: how to fix it. Anyone willing to help or has experience this problem before and knows the solution? Here some (hopefully) useful information below:

Currently using 4.86.1 REBUG LITE on PS3 Slim 21xx series, I have latest versions of IRISMAN, MULTIMAN, webMAN, sMAN, Managuns, Rebug toolbox, homebrew all installed.


Thank you to whomever may be able to help or provide information to fix this problem, I greatly appreciate it.

 

[ElGris]

Have you tried powering on the console from the power button of the PS3 while the DS3 is already paired? It is still unpaired when you press the home button to turn on the gamepad? Try that.

 

[sandungas]

Try to reset it by inserting a toothpick in the tiny hole that have at the back
Next thing i would suspect is the battery... but mostly because i never heard about this problem before so im a bit lost

 

[auracle2g]

Have you tried powering on the console from the power button of the PS3 while the DS3 is already paired? It is still unpaired when you press the home button to turn on the gamepad? Try that.

Yes, that way does work, it will stay paired that way. If I try to turn the console on with the PS3 controller, it will lose pairing/sync. Yes, I have tried many times to resetting the controller itself in the back with a pin. The battery itself works very well, long charge that holds, and has no problems if I start the console at the PS3 itself. I had read somewhere, the developer himself posting that something like this was fixed in the latest version of sMAN... and I did update to that. It actually did work for a very short time, maybe a 2 boots from the controller, and then I found it started to begin desyncing like usual. That does make it *seem* homebrew related, but I have no proof and truly do not know.

Still baffled, anyone else experience this or have just have some input? Thanks.

 

[JJ JONES]

Yes, that way does work, it will stay paired that way. If I try to turn the console on with the PS3 controller, it will lose pairing/sync. Yes, I have tried many times to resetting the controller itself in the back with a pin. The battery itself works very well, long charge that holds, and has no problems if I start the console at the PS3 itself. I had read somewhere, the developer himself posting that something like this was fixed in the latest version of sMAN... and I did update to that. It actually did work for a very short time, maybe a 2 boots from the controller, and then I found it started to begin desyncing like usual. That does make it *seem* homebrew related, but I have no proof and truly do not know.

Still baffled, anyone else experience this or have just have some input? Thanks.

I have the same problem

 

[ElGris]

This is a hardware issue and has to do with the BGAs under the wifi module. The contact that maintain the BT standby that triggers the wireless turn on is not making a proper contact with the module. I've discovered this issue due a change module I made myself (third one actually using no BGAs). This time I found out the home button didn't turn on the console, so my direct guess is that something happened with that area of the soldering. I was too lazy and left it like that lol, it isn't somthing serious after all.
I discard a software issue 'cause this works at a low level hardware, and in this case I'd do a soft reflow using flux. Of course, you could damage the module if you don't know what are you doing, so I recommend you leave it like that.

 

[auracle2g]

This is a hardware issue and has to do with the BGAs under the wifi module. The contact that maintain the BT standby that triggers the wireless turn on is not making a proper contact with the module. I've discovered this issue due a change module I made myself (third one actually using no BGAs). This time I found out the home button didn't turn on the console, so my direct guess is that something happened with that area of the soldering. I was too lazy and left it like that lol, it isn't somthing serious after all.
I discard a software issue 'cause this works at a low level hardware, and in this case I'd do a soft reflow using flux. Of course, you could damage the module if you don't know what are you doing, so I recommend you leave it like that.

I don't believe it is hardware related, honestly. Nothing has suggested that so far- in fact, it working after the software update for a short time suggests the opposite, imo. I will keep searching for answers, thank you.

 

[ca$e]

I don't believe it is hardware related, honestly. Nothing has suggested that so far- in fact, it working after the software update for a short time suggests the opposite, imo. I will keep searching for answers, thank you.

Did it work on OFW 4.86 ?? I'm assuming yes.

I have had weird issues on some PS3 slims , not the same as yours but I solved it by installing OFW twice before modding and then whatever custom firmware twice aswell. Then I install homebrew.

Generally when I mod a console I'll formate the whole system to factory fresh. Then I'll update to 4.86 OFW twice. Then use psxploit to patch, then Install cfw twice.
Make sure you enable qa flag. Then install homebrew.

Installing firmware twice ensures it installed correctly and has fixed issues with webman and wifi for me


Sent from my LM-X120 using Tapatalk

 

[auracle2g]

Did it work on OFW 4.86 ?? I'm assuming yes.

I have had weird issues on some PS3 slims , not the same as yours but I solved it by installing OFW twice before modding and then whatever custom firmware twice aswell. Then I install homebrew.

Generally when I mod a console I'll formate the whole system to factory fresh. Then I'll update to 4.86 OFW twice. Then use psxploit to patch, then Install cfw twice.
Make sure you enable qa flag. Then install homebrew.

Installing firmware twice ensures it installed correctly and has fixed issues with webman and wifi for me


Sent from my LM-X120 using Tapatalk

Yeah, I've only ever been on 4.86, as I bought the PS3 this past week. I remember the old Android days for me when I'd mess with CFW and do exactly what you're describing above, and I now have great confidence your advice will make a change. Thank you! I'll update if it does the job.

Question for anyone: I have many games installed to my HDD in PSN .pkg. If I reinstall OFW over CFW, would that erase all of the games as well?

 

[auracle2g]

fixed

 

[auracle2g]

Alright, here's the solution:

Take your HDD out of the PS3, plug into your PC and completely format it (everything gets erased), and reinstall OFW 4.86. Start fresh again, if you'd really like the missing feature.

It now works for me, everytime.

So, I don't know how it got this way, but I'd imagine trying to be minimalistic and careful with homebrew and how much you modify.

It's a pain in the butt to lose everything but I'm glad I can now turn my console on and off with the controller with zero problems! Thanks all.

 

[ElGris]

Nice that you could get it to work on that way, but I tried what you did twice when I was testing this and it didn't fix it at all haha. Oh, well..

 

[psydefx]

Hello guys,

Whenever I use my OEM Wireless Dualshock 3 Sixaxis to wirelessly boot my PS3 up with the PS Button, the controller unsyncs and has to be plugged back into the console to regain sync/pairing. I've tested every other scenario and it is specifically this problem as the only way this happens. Can reproduce it everytime, never witnessed any other way.

So I'm stuck, I don't know what's up: how to fix it. Anyone willing to help or has experience this problem before and knows the solution? Here some (hopefully) useful information below:

Currently using 4.86.1 REBUG LITE on PS3 Slim 21xx series, I have latest versions of IRISMAN, MULTIMAN, webMAN, sMAN, Managuns, Rebug toolbox, homebrew all installed.


Thank you to whomever may be able to help or provide information to fix this problem, I greatly appreciate it.

i recently started having this same issue on my slim 2001a. tested two other ds3 to rule out controller is bad. switched from dex to cex and tested various 4.xx cfws and still not fixed. problem is the console i think smh :/

 

[PSNDOOD]

fixed

I have this problem, i will try formatting in my pc but i doubt that will fix it as i think i had this issue before installing cfw… i bought this ps3 slim second hand and theres burn marks on the broken and burnt out bluray drive.

I think maybe something set on fire? Lol but anyway where the chip that i would need to reflow? Whats it called?

 

[arcadekidflo]

OEM controllers do give that problem . If you restored your console than used only that controoler it may have tricked it into working ? Who knows .

 

[bguerville]

Pad issues can have multiple causes, they can be hardware based (many dodgy pad clones out there or just a malfunction on either side of the BT connection) or software based.

If reformatting fixed his sync issues, the OP probably experienced problems caused by a conflict between the numerous homebrews he installed or some customisation he applied.
Among other things, he mentioned having installed webman and sman for instance, 2 plugins that cannot coexist, this kind of thing has the potential to create undefined behaviour.
Ultimately he never found the exact cause of his pad sync issues.

You can reformat the drive if there's nothing on it you care to keep otherwise before going for the nuclear option, you might consider testing a few things to see if you can narrow down the issue, for instance you could try to
1. Disable plugins in boot_plugins.txt
2. Disable Cobra
3. Reset the xRegistry pad related settings (make a backup of the xRegistry.sys file before beginning to edit and test and be aware that xRegistry.sys is a crucial system file, messing with it can potentially lead to a full OS reinstall with data loss same as reformatting)
4. Install OFW 4.8x as it's easy to reacquire jailbreak afterwards without loosing any data

Remember to test only one change at a time, and reboot after making any of the suggested changes above, only then will a change be applied and you will be able to test your pad sync.

Before messing with your setup, you should also dump your eid_root_key (the internal hard drive encryption key) if you haven't done it yet, and while you are at it, take the opportunity to dump your NOR too, keep those files safe they might save your bacon one day.

 

[PSNDOOD]

Pad issues can have multiple causes, they can be hardware based (many dodgy pad clones out there or just a malfunction on either side of the BT connection) or software based.

If reformatting fixed his sync issues, the OP probably experienced problems caused by a conflict between the numerous homebrews he installed or some customisation he applied.
Among other things, he mentioned having installed webman and sman for instance, 2 plugins that cannot coexist, this kind of thing has the potential to create undefined behaviour.
Ultimately he never found the exact cause of his pad sync issues.

You can reformat the drive if there's nothing on it you care to keep otherwise before going for the nuclear option, you might consider testing a few things to see if you can narrow down the issue, for instance you could try to
1. Disable plugins in boot_plugins.txt
2. Disable Cobra
3. Reset the xRegistry pad related settings (make a backup of the xRegistry.sys file before beginning to edit and test and be aware that xRegistry.sys is a crucial system file, messing with it can potentially lead to a full OS reinstall with data loss same as reformatting)
4. Install OFW 4.8x as it's easy to reacquire jailbreak afterwards without loosing any data

Remember to test only one change at a time, and reboot after making any of the suggested changes above, only then will a change be applied and you will be able to test your pad sync.

Before messing with your setup, you should also dump your eid_root_key (the internal hard drive encryption key) if you haven't done it yet, and while you are at it, take the opportunity to dump your NOR too, keep those files safe they might save your bacon one day.

I think it might have been a HDD issue, as i suspect it was quick formatted before it was sold to me.

I ended up ignoring the problem for the moment and just downloading tons of ps3 games filling the HDD, and now it miraculously works!

I don't know but maybe the ps3 was reading some left over 1s and 0s that werent completely formatted? Anyway all is good now, thanks as always

 

[puddii]

I have this issue too! So following this advice from the legend:

Pad issues can have multiple causes, they can be hardware based (many dodgy pad clones out there or just a malfunction on either side of the BT connection) or software based.

If reformatting fixed his sync issues, the OP probably experienced problems caused by a conflict between the numerous homebrews he installed or some customisation he applied.
Among other things, he mentioned having installed webman and sman for instance, 2 plugins that cannot coexist, this kind of thing has the potential to create undefined behaviour.
Ultimately he never found the exact cause of his pad sync issues.

You can reformat the drive if there's nothing on it you care to keep otherwise before going for the nuclear option, you might consider testing a few things to see if you can narrow down the issue, for instance you could try to
1. Disable plugins in boot_plugins.txt
2. Disable Cobra
3. Reset the xRegistry pad related settings (make a backup of the xRegistry.sys file before beginning to edit and test and be aware that xRegistry.sys is a crucial system file, messing with it can potentially lead to a full OS reinstall with data loss same as reformatting)
4. Install OFW 4.8x as it's easy to reacquire jailbreak afterwards without loosing any data

Remember to test only one change at a time, and reboot after making any of the suggested changes above, only then will a change be applied and you will be able to test your pad sync.

Before messing with your setup, you should also dump your eid_root_key (the internal hard drive encryption key) if you haven't done it yet, and while you are at it, take the opportunity to dump your NOR too, keep those files safe they might save your bacon one day.

1. The only plugin I have in boot_plugins is webman mod. I had other various plugins installed (never sman like OP) at some point, but those are uninstalled at the moment.
2. Disabling cobra works for exactly 1 boot. After another power cycle, it is back to not syncing after power up from the controller
3. No idea what I'm doing as far as editing the xRegistry, so I'm not going to mess with that without knowing.
4. Without the availability of the bgtoolset, I'm not going to install and OFW.

I also tried reintalling evilnat 4.89. While in the install screen, the controller was able to sync with the console without plugging it in.

Does anyone have anything for me to try? Any tips or tricks? I would rather not start from scratch with an HD format, and while the issue exists I can do some testing. It isn't a make or break issue, all ai have to do is plug it in after booting, but it would be nice to resolve it lol