I noticed after loading the cm7 alpha that my NT's MAC address had changed. I'm speculating that we're all using the same one rather than something unique. At this stage in the game it doesn't matter much unless someone has two devices on one network. But if I'm correct it's something that should be dealt with eventually.
This is my "new" MAC, 08:00:28:12:03:58. What's yours?
LordGibson said:
This is my "new" MAC, 08:00:28:12:03:58. What's yours?
Click to expand...
Click to collapse
Yep, the same as yours.
This thread on the Kindle Fire discusses the issue some.
I am using the SD Card version of CM 7 and do not believe I am experiancing this issue. I' m not 100% sure but I use MAC Address filtering on my wifi router and had no problem connecting when running the ROM.
I'm on stock right now and do not have the SD handy but I will verify later.
Obviously if my mac address had changed I shouldnt have been able to connect without adding the "new" mac to the router config.
Edit: Confirmed that I am NOT affected by this when running off the SD Card.
Land Master said:
I am using the SD Card version of CM 7 and do not believe I am experiancing this issue. I' m not 100% sure but I use MAC Address filtering on my wifi router and had no problem connecting when running the ROM.
I'm on stock right now and do not have the SD handy but I will verify later.
Obviously if my mac address had changed I shouldnt have been able to connect without adding the "new" mac to the router config.
Click to expand...
Click to collapse
Agreed. It sounds like it didn't affect you. That's how I noticed - had to authorize the new address on a dozen networks this week
LordGibson said:
This thread on the Kindle Fire discusses the issue some.
Click to expand...
Click to collapse
Later in that thread they talk of using the stock wlan_loader to restore the original MAC. I gave it a go but that didn't work. It didn't fail but didn't restore the MAC.
Figured I give the NVS stuff a try. I was able to create nvs_map.bin using the instructions from this thread but no matter where I put the edited file the driver stated: "No Nvs, Setting default MAC address".
For those with a single Nook this isn't a problem but as soon as two are on the same network problems will ensue.
LordGibson said:
This thread on the Kindle Fire discusses the issue some.
Click to expand...
Click to collapse
Quick Workaround: Use the instructions in the mentioned Kindle Fire thread. You will need to save the calibration file as /system/etc/wifi/WifiBackupCalibration. Make sure the permissions are correct.
Details: The wlan_loader program is called by /init.omap4430.rc with the option to load the eeprom calibration file but that file doesn't exist (simple typo WifiBackupCalibration versus WiFiBackupCalibration, capital F). If wlan_loader can't find that file it uses the default MAC address. I'm not sure what the long term fix is because it looks like our two options are the default MAC or one that you hex edit into the calibration file. I let the development team know of the typo. Hopefully they have resources on how to give a distinct MAC to each.
I still had my old MAC from a previous dhcp lease file and it is now working great with the stock Nook MAC.
EDIT: This is only for those using the initial CM7 alpha as it is already fixed in the next version.
jeffml said:
Quick Workaround: Use the instructions in the mentioned Kindle Fire thread. You will need to save the calibration file as /system/etc/wifi/WifiBackupCalibration. Make sure the permissions are correct.
Details: The wlan_loader program is called by /init.omap4430.rc with the option to load the eeprom calibration file but that file doesn't exist (simple typo WifiBackupCalibration versus WiFiBackupCalibration, capital F). If wlan_loader can't find that file it uses the default MAC address. I'm not sure what the long term fix is because it looks like our two options are the default MAC or one that you hex edit into the calibration file. I let the development team know of the typo. Hopefully they have resources on how to give a distinct MAC to each.
I still had my old MAC from a previous dhcp lease file and it is now working great with the stock Nook MAC.
Click to expand...
Click to collapse
I posted a link to this thread in the Alpha ROM thread, I'm also going to PM Celtic later today and see what he says about it - this a pretty strange bug but it probably has a very easy fix.
Related
I have been having trouble connecting to my work VPN with the G-Tablet. I have since tried going to ZPad 3.0 in hopes this would fix the issue. However, no luck. The VPN server is reporting an event error of 20209.
After a few hours of looking on other forums it turns out this have been an issue since Android 2.1. They have either intentionally left out the encryption module from PPPD or it was forgotten in the build. The 'fix' is to copy the PPPD file from a version prior to 2.1 (Android 1.5?) and save it to the System/xbin directory. However there is an argument over if should go into system/bin for 2.2.
Does anyone have more information on this - or better yet a fix/update? Any help on this would be appreciated.
which ROm are you using
stock ROM doesn't have VPN at all.
justauser said:
stock ROM doesn't have VPN at all.
Click to expand...
Click to collapse
I'm using ZPAD 3.0 ROM at the moment.
I have narrowed it down to a problem with the MPPE 128 encryption. I have found a PPPD that is supposed to fix the problem (see link below), but I don't now how to get it to the system directory. How do you mount system as R/W?
Alternate PPPD:
H***://melko.hiljanen.com/~qvr/android/ppp/
Root explorer will allow you to mount it that way
Sent from my DROIDX using Tapatalk
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ditto!!!!!!!!
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
The lastest info I have been able to collect on this issue is that it has been known at google since 2.0 was released. They were having a problem keeping a connection using MPPE 128 over PPTP so instead of releasing something that did not work right, they removed support for it until a later date. Said date has not been determined.
I will keep you posted as I find out more.
roebeet said:
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
Click to expand...
Click to collapse
I came across this too. Since the ppp directory exists under system/etc I have made the assumption that there is support for it (at least under ztab 3.0). In order to check using the method above we would need a terminal app or some other way to run the commands. If there is a way to do it natively I am too new to know.
Any devs willing to tackle this issue?
Newanzer said:
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
...
I will keep you posted as I find out more.
Click to expand...
Click to collapse
No luck. The Net Admin decided it would be too much work just for a tablet test (and his iPAD VPN work just fine thank you). Anyone willing to try a L2TP test?
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
nephelim said:
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
Click to expand...
Click to collapse
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
I confirm that the advent vega rom has the same problem.
Unable to use vpn.
Newanzer said:
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
Click to expand...
Click to collapse
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
rcgabriel said:
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
Click to expand...
Click to collapse
That could be worth the check. I would like to see a list of exactly what his kernel supports before I try though.
[EDIT]: Checked change log. VPN module in kernel not mentioned.
Looking over the list of known issues at Google, this problem has been known for a while. The fact that Google hasn't addressed it worries me a bit. It is possible that since phones are the largest part of their OS client, VPN isn't a high priority. They may be waiting for the open source community to solve their problem for them.
Was able to get VPN working
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
there is very easy installation get and run vpn frome purevpn........
brainyjd said:
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
Click to expand...
Click to collapse
Sorry for asking this noob question, but is this VPN fix only for Cyanogenmod, or will work with others, such as TnT Lite?
I'm running TnT lite and there no's VPN setup option.
tnt is missing the vpn shortcut
use VPN Show
Kazuyuki Eguchi/Tools
found in android market to access the vpn menu
i have used with sucess on most roms open vpn and open vpn settings
with out problems just by install them and setting it to auto run at start
with install to xbin and create a folder on internal sd "openvpn"
then place a vpn.conf file there
then connect this cause an error but causes super user to give it root rights
after that all my vpn,s work with out going near openvpn
purevpn said:
there is very easy installation get and run vpn frome purevpn........
Click to expand...
Click to collapse
Please elaborate...
Thanks!
As I sit here at work my mind start to think. There is a host file on the Nook Color that is used just as the host file on a Windows machine is used. The Nook Color can auto update itself with out knowledge of the user. Why not monitor the ip address the Nook Color downloads the Side Loader update zip file from and block that address in the host file? That is better then renaming the OTACert file and if the site isn't found by the device the device will not try and update its self.
I thought of it now one of you go figure it out....here is what you have to do;
1. Make sure your on 1.0.0 firmware on the B&N Nook
2. Run Monitoring program on your router to see incoming data and what IP's are being utilized.
3. Run WIFI on Nook
4. Look for new data (side loader being downloaded from B&N)
5. Block that IP address in the hosts file
6. Reboot nook and see if it still tries to update its self.
Post back results.
2nd Idea:
I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access rights through adb or root explorer.
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
mtl171 said:
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
Click to expand...
Click to collapse
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
xboxexpert said:
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
Click to expand...
Click to collapse
Aparently you can not chmod anything in /media folder
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
wvcachi said:
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
Click to expand...
Click to collapse
That works good but what if i wanted to stay on 1.0.1 with out updating...
How come some people get the auto update and some don't? I've been on 1.0 since before Christmas and haven't been forced into an update. I've even been sitting in B&N for hours at a time.
xboxexpert said:
That works good but what if i wanted to stay on 1.0.1 with out updating...
Click to expand...
Click to collapse
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
wvcachi said:
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
Click to expand...
Click to collapse
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
xboxexpert said:
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
Click to expand...
Click to collapse
It looks like that was based on one post that the poster later attributed to something else (read thread http://forum.xda-developers.com/showthread.php?p=10390633#post10390633).
So I see no reason not to disable otacerts on any firmware right now.
Is there a file in the files structure that houses the WPA passphrase. I have looked around in \system\etc\wifi but none of those files seem to be what I am looking for. I have a feeling it is encrypted in some file but I thought I would ask if anyone knows. Most of the devices tell me that the passphrase is unchanged when i go into the settings of already configured networks. This does not help me if i forget what the passphrase is. Thanks in advance.
jschauf said:
Is there a file in the files structure that houses the WPA passphrase. I have looked around in \system\etc\wifi but none of those files seem to be what I am looking for. I have a feeling it is encrypted in some file but I thought I would ask if anyone knows. Most of the devices tell me that the passphrase is unchanged when i go into the settings of already configured networks. This does not help me if i forget what the passphrase is. Thanks in advance.
Click to expand...
Click to collapse
If you are rooted you can use WiFi key recovery from the market to recover your passphrase. I have no idea where it gets this information though, you could always ask the dev I imagine.
you will need root to read /data or adb.
the wpa psk is clear text in
/data/misc/wifi/wpa_supplicant.conf
polobunny said:
If you are rooted you can use WiFi key recovery from the market to recover your passphrase. I have no idea where it gets this information though, you could always ask the dev I imagine.
Click to expand...
Click to collapse
That helps for my rooted phone but not for the stupid Kindle Fire one of my co-workers has. That is the device I am really trying to extract the passphrase from. I will look at that app for my phone though.
jschauf said:
That helps for my rooted phone but not for the stupid Kindle Fire one of my co-workers has. That is the device I am really trying to extract the passphrase from. I will look at that app for my phone though.
Click to expand...
Click to collapse
Well you need root either way. :/
polobunny said:
Well you need root either way. :/
Click to expand...
Click to collapse
Figures, guess I will have to figure something else out.
you MIGHT be able to do it with adb without root
if you have adb on a computer somewhere try
adb pull /data/misc/wifi/wpa_supplicant.conf
Managed to fix my wifi mac address problem with some info read in this thread:
forum.xda-developers.com/showthread.php?t=1131649
all performed using linux,
connect phone to pc using in terminal
adb shell
dd if=/dev/block/mmcblk0p3 of=/sdcard/filename.img (stored image of block on sdcard)
exit
exit
disconnect then reconnect phone to pc this time allowing access to sdcard.
in terminal mount the image for editing
mount -o loop /source/filename.img /destination/
using a hex editor modify '/wifi/wlan_mac.bin' with wanted address
save
unmount /destination/
the filename.img has now been modified and needs to be returned to the phone
remove the phone then reconnect and using 'adb shell'
su
chmod 777 /sdcard/filename.img
dd if=/sdcard/filename.img of=/dev/block/mmcblk0p3
reboot
now after the reboot connect your phone to the wifi and it will be using your new address
Original question below:
got 2 of these Atrix phones.
i have rooted both following this guide
wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide
now my one has this installed:
cm-7-20121014-NIGHTLY-olympus.zip
the wifes is still stock.
now we both have been experiencing wifi problems, which i have traced to both phones having the same wifi mac code
98:4B:4A:5D:8D:4C. Resulting in the router not being able to distinguish between them, a right mess.
i have tried following this guide to change my mac address
pocketnow.com/tweaks-hacks/motorola-atrix-4g-how-to-change-wi-fi-and-bt-mac
but changing the address in this file has no effect, its as though the mac address above is a spoof. Not the address stored in /pds/wifi/wlan_mac.bin
i have also tried from terminal 'busybox ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx'
this also does not change my address.
others mention to change the contents of nvram.txt here:
/etc/wl/nvram.txt
this also has made no change
the 2 file locations mentioned contain different mac addresses from the one above.
which file contains this code '98:4B:4A:5D:8D:4C' ?
How do i change the mac address?
i think mac address related to hardware so you can't change it. I have flashed several roms but the mac address is constant, the only change is device name.
Sent from my MB860 using xda app-developers app
lambcutlet said:
which file contains this code '98:4B:4A:5D:8D:4C' ?
How do i change the mac address?
Click to expand...
Click to collapse
/pds/wifi/wlan_mac.bin looks like the right place. But be aware that messing up your PDS could mean quite bad consequences for your phone.
I'd probably dump the entire PDS partition into a file and back it up somewhere if I were you.
voncount said:
i think mac address related to hardware so you can't change it. I have flashed several roms but the mac address is constant, the only change is device name.
Click to expand...
Click to collapse
Nope, wrong.
It's true a MAC is a hardware address, but it's not true it cannot be changed.
ravilov said:
/pds/wifi/wlan_mac.bin looks like the right place. But be aware that messing up your PDS could mean quite bad consequences for your phone.
I'd probably dump the entire PDS partition into a file and back it up somewhere if I were you.
Nope, wrong.
It's true a MAC is a hardware address, but it's not true it cannot be changed.
Click to expand...
Click to collapse
pds backup was performed. My address is different in the 'wlan_mac.bin' file, probably the original F8:7B:7A:xx:xx:xx. i did manage to change its contents but still it appears to be over-ridden by '98:4B:4A:5D:8D:4C'
its weird that both phones have the same mac address
also noticed the bluetooth address is different 00:11:22:33:44:55
there is a program somewhere on my phone over riding the original addresses.
does anyone know what it could be?
has anyone else used the same guide as me to root the phone and ended up with the same mac and bt addresses?
I'm looking for some help verifying a few bits of information before I take a leap and risk bricking my phone. I need to change my bluetooth address. With any luck back to my original hardware address. I do have the original address, as "btnvtool -p" outputs a different address than is reported in 'about phone' -> 'status'. I problem is that both my wife and I have the same phone with the same ROM history, and now we both have the same improper mac address.
By way of links provided by another helpful users I have partial information in Russian. http://4pda.ru/forum/index.php?showtopic=420801&st=6840#entry28414922 post 6853. I think I understand what to do via google translate and my partial understanding of how this works. The post points me to the /misc partition but I can't find any useful information about the partition for this phone that would backup the claims. Also the specific location that the post references, offset 4000, contains a string "ANDROID-BOOT!". While "ANDROI" is hex of 414E44524F49 which matches my incorrect mac address, the fact that it says "BOOT" makes me worry about changing it.
I'm hoping someone can help me any verify that this string isn't part of the boot process, or that the /misc partition isn't required to boot recovery. I feel fairly confident that I could create a flashable zip to restore a backup of this partition if needed. Below is my cleaned translation of the Russian post. If anyone with an e970 and a proper BT address could complete the first half, dd the partition to a file and check out the contents in a hex editor, I would feel much better about doing the rest.
Code:
Hello, using this method you can restore your original Bluetooth addresses. The active mac address is in raw MISC partition at hex offset 4000, it is not spelled out or anything.
perform the following (root is required)
ADB shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.img
and get at the file on the SD card and in a HEX editor zero the MAC address starting at hex offset 4000, save the file. Save the changed file to your phone:
su
dd if=/sdcard/misc.img of=/dev/block/platform/msm_sdcc.1/by-name/misc
reboot
After rebooting the details in the “About Phone” should show the real MAC BT.
----------
So I found a little corroborating evidence to this post. I found this post about the LS970(Sprint LGOG) stating that "All rooted LGOG Bluetooth MAC addresses are 41:4E:44:52:4F:49". Reading the thread a bit, I found a link to a "BT MAC FIX" script found with this kernel.
Looking at what the file does, it uses btnvtool to get the real mac and writes it to byte 16384 ( hex 4000 ) of the misc partition. Seeing as this file has people confirming it works, I took the leap. It worked. Problem solved.
Sound like to me this is a problem as old as unlocking with freegee. Could be wrong but that seems like the common denominator to me from the posts I was reading. And yes for the record, now the dump of the misc partition now reads "******D-BOOT!" *s to hide my real mac.
***Warning, 2015-01-12, This Fix as is doesn't work and causes problems with CM12 on the E970. Will post in thread with details.
I have the exact same issue with mine and my wife's phone. I tried this, and it seems like it should work, but after I reboot my phone, the contents of misc revert to the original (ANDROID...). Any thoughts?
mindstormsguy said:
I have the exact same issue with mine and my wife's phone. I tried this, and it seems like it should work, but after I reboot my phone, the contents of misc revert to the original (ANDROID...). Any thoughts?
Click to expand...
Click to collapse
I believe everyone that used freegee to root/unlock have the corrupted BTmac address. I also believe that it is only an issue when two of these devices try to use BT in close proximity, but you never know what device the person beside you will have.
I had not done anything about my BT until just now. The .zip just puts a script in the userinit.d folder. The script is run every boot. I do not recall what my BTmac address was, but the script does change it from the default.
I deleted the script and rebooted. My BTmac address reverted back to the default. I restored the script and my BTmac address changed back. This shows that the change is not permanent, and the script needs to be run every boot.
Did you flash the .zip, or just extract and run the script?
I've recently upgraded my E970 to CM12 nightly. Just like previous roms the BT Mac address is corrupted and results in my pairing being invalid. My mac address currently reports in "About Phone" as 00:00:00:00:5A:AD. Clearly this is incorrect.
When I tried to install this fix. The init.d script was placed properly, but did not repair the mac address as it did previously. This might be a one off case, but after the script was installed, my phone started acting funny, over heated, and completely drained the battery. The charger I regularly use, an iPad 2.1 amp failed to charge the phone. All it would do was turn on the red notification light solid. I was still able to use the computer usb ports to enter download mode, and start entering the off-charge mode. This port didn't give enough power to fully enter the off-charging mode. The phone made it to the first icon and then shut off, no progress was made.
I needed to switch to a lower output charger before I could gain charge to 5% and boot. As the OS booted it reported 0% charge. I was able to enter airplane mode and reboot. After the reboot the phone functioned well enough to use Solid Explorer to delete the script file from /data/local/userinit.d . After deleting the file my phone was back to functional with the bad mac address.
As I find info I will post it here.
2015-01-13 Update -----
Running the steps of the script file manually, results in a error "dd: stdout: Illegal seek" . Trying to read (if) instead of write (of), I get the same Illegal seek. Might this be part of a new protection with lollipop? I tried editing a dump of the partition as I suggested originally and writing the whole 16mb back. This completes without error, but when I read the partition again the modification was not saved.
Either way my BT Mac address with CM12 doesn't match the expected 41:4E:44:52:4F:49 to match the ANDROID from the file dump, so where is the OS picking up the new address?
Still works for CM11
I noticed my phone and my wifes also had the same bluetooth address. This was messing up my car link. I ran the script and now it shows that I have a different address. I will keep an eye out and make sure nothing else gets messed up. Thanks. I was looking for a fix for some time....