Ok.. hesitant to post up.. don't want anyone to f' up there wifi units but.........
Ok Basically... simple change.. and a large portion of this is thanks for LinuxKid who told me about the HT40 change.. I just played around a little to find out what works best for me.. so big thanks to him 
Now... do this at your own risk... If you have a mistype or screw up, or something goes wrong its possible you will not be able to connect back into the wifi module to fix, thus rendering the wifi module screwed and you will either need to buy a new one
or send back to DJI to get repaired.. If they even repair them.. I'm sure they can.. but if they do is another story..
This is an easy change, but not for someone not familiar with linux... Fark even using txt editor VI is pretty tricky hehe..
I would suggest anyone who wants to do this to
read up on "HT40 vs HT20 wifi modes". From my understanding if you are in an area where you have alot of other interferance setting HT40 can actually give worse results than using HT20... Basically ht20 is the default and provides 20mhz channel.. Setting ht40 provides 2x20mhz channels and is kind of overlaps into other channels, thats why it can give worse results if you are in an area with heaps of wireless activity... which I am..
Odd thing is.. in my suburban area where I fly.. there are at minimum 10-15 other access points that I pickup, so in theory I should get worse results using HT40.. but yeah I don't... I did actually have to play around with the channel to get optimal results, but once I did (and few other settings its worked a treat at 640x480).
**** SO AGAIN... READ UP ON ALL OF THIS AT THIS SITE.. http://wiki.openwrt.org/doc/uci/wireless .... ITS GREAT.... THEN READ AGAIN ON GOOGLE... ****
I TAKE NO RESPONSIBILITY IF YOU BRICK YOUR WIFI MODULE... Also you need to read the site as there are some combinations of options/channels that will not work... I am not sure if you do this if the wifi module will not start up the HOSTAPD process (which basically runs the access point) will means the wifi module will not let you connect
or if it just still run hostapd but just complain/error, but still be useable...
There are a tonne of options you can change, and you can read about then on the openwrt site I posted above.. but I will just mention what I changed to get great 640x480 @ 30 FPS results..
so basically.. you ssh into 192.168.1.1 which is the phantom and have a look in /etc/config/wireless
You config will probably look like this
config wifi-device 'radio0'
option type 'mac80211'
option channel '6'
option hwmode '11ng'
option path 'platform/ar934x_wmac'
option htmode 'HT40-'
list ht_capab 'LDPC'
list ht_capab 'SHORT-GI-40'
list ht_capab 'TX-STBC'
list ht_capab 'RX-STBC1'
list ht_capab 'DSSS_CCK-40'
option country 'BO'
option txpower '17'
config wifi-iface
option device 'radio0'
option network 'lan'
option mode 'ap'
option wds '1'
option ssid 'FC200_01f825'
option encryption 'none'
option hidden '1'
Parts is bold, is what I changed...
So the first is the channel.. for me originally It was on channel 5.. Normally its good practise to run wifi or channel 1, 6 or 11... HOWEVER READ UP ON THE SITE I MENTIONED TO CONFIRM WHAT CHANNELS WORK WITH WHAT HT20/40 MODES..
So I changed first to channel 11 (from 5)... and I changed option htmode 'HT40-' originally this was set to HT20. There is mode HT40- HT40+ HT20 HOWEVER READ UP ON THE CHANNELS YOU USE WITH EACH MODE!!!!!!!!!!!!!!!!!!
Doing that I was able to run 640x480 @ 30 FPS for first time ever but the range sucked balls... so I changed it to channel 6.. That improved range quite a bit..
The second change I made was
list ht_capab 'SHORT-GI-40'
originally that was
list ht_capab 'SHORT-GI-20'
So I basically changed it from 20 to 40
And lol yeah thats it... Again I can't stress enough... read about what all the settings do.... HT40 may not work on all phones... so you may find your phone can not connect but hopefully your PC/Laptop can so you can change the setting back.
So in summary.. I made these changes
option channel '6'
the 6 was a 5, then 11 then settled on 6
option htmode 'HT40-'
original setting was
option htmode 'HT20'
last thing
list ht_capab 'SHORT-GI-40'
that was originally
list ht_capab 'SHORT-GI-20'
You may find just changing channels IS ALL YOU NEED TO RUN AT 640x480 @ 30FPS!!!! without the ht20/40 stuff
Or you might need to change to HT40... or you might need to change the SHORT-GI-40 setting.
Some of you may find changing all of it a) makes it 640x480 work nicely... b) doesn't make any diff and same as before... and worst case c) bricks wifi unit.
Can't stress enough.... if your not familiar with linux have a long hard thing about if this is worth it... if things go bad I mean....
Again, big thanks to Linuxkid who initially steared me in the direction of HT40 which then led to me optimizing slightly and finally getting 640x480 @ 30FPS mode working...
As some of you said... seems to work on some phones... but not 98% of them though... anyways I have put the changes I described into my mates vision + (non v3) and now 640x480 @ 30FPS works great on his Samsung S4, and my vision + (non v3) works great on Samsung S5.
Another friend who has a vision + and a Samsung s5 (same android version as mine) we left default of ht20 on... but we changed from his default channel 9 to channel 6 and he was able to run 640x480 @ 30 fps.. which is odd!!! but yeah just a channel change was all that was needed/
Oh yeah I have the tx power boosted to 17dbm as well... but I found initiallly 640x480 @ 30FPS and even 15 FPS doesn't even work from like 3 feet away lol.. so any boosting can't fix that.
BTW The changes made on the phantom in /etc/config/wireless are for the HIDDEN ssid that the RE connects to.... the RE then runs another SSID called Phantom_xxxx which your device connects back to... problem is if hidden SSID on the wifi unit in Phantom is screwed, you device will not be able to connect to RE.. and even if it coudl.. the RE could not connect lol... so yeah....
Oh yeah you can ignore the country code and txpower setting in my /etc/config/wireless... It is not how you change the TXPOWER, I was playing around with that a while ago and just never took it out... the commands used to work, possibly on phantom vision (non plus???) I dunno, but aren't suported on vision plus, to change your txpower you need to do other stuff..
***
If you guys want I can provide my script which does some checks.. so if you make the changes and if something f's up and you can not connect back into the wifi unit... the system will automatically restore the old wireless config and fix it up.. this saving you from bricking the unit 
***
As I said.. only a few changes.. but a lot of reading needs to be done before deciding if you want to go through with it... maybe I am just a bit dramatic.... i dunno.. I've been using linux for 15 years... and I was kinda scared each time I did a reboot lol..... I must say though 640x480 @ 30fps is very clear :]
and again.. thanks to Linuxkid!!!!