There seems to be some success with this, so if you are having battery drain issues turn off your touch sounds and unlock sounds. Audiodriver_1 seems to be constantly starting while the phone is sleeping which is consuming power. Turning these sounds off seems to fix the problem for now

Sent from my LG-VM670 using Tapatalk

how do I get my original Mac address?

Sent from my Amazon Kindle Fire using xda premium

Originally Posted by pbailey212

There seems to be some success with this, so if you are having battery drain issues turn off your touch sounds and unlock sounds. Audiodriver_1 seems to be constantly starting while the phone is sleeping which is consuming power. Turning these sounds off seems to fix the problem for now

Sent from my LG-VM670 using Tapatalk

I'll give it a try and report.

Originally Posted by lovejoy777

how do I get my original Mac address?

Sent from my Amazon Kindle Fire using xda premium

You can change it as long as you know your original MAC Address.

http://forum.xda-developers.com/show...&postcount=458

I noticed that the wall charger will not work unless you plug it in while the screen is on. So keeping the screen on initially I was able to charge without problems.

sorry you miss understood, I'm unsure how to find my original mac address, do I have to flash a stock rom to be able to see it?

Sent from my Amazon Kindle Fire using xda premium

Originally Posted by lovejoy777

sorry you miss understood, I'm unsure how to find my original mac address, do I have to flash a stock rom to be able to see it?

Sent from my Amazon Kindle Fire using xda premium

You can load CM7 rom or backup of whatever rom you were using, or restore to stock.

Originally Posted by TheKid2

You can change it as long as you know your original MAC Address.

http://forum.xda-developers.com/show...&postcount=458

I'm not sure that's necessarily completely true. I don't think you need to know the original MAC address.

I blindly issued the command in the above post WITH THE XX:XX:XX:XX:XX:XX left as 'X's. Obviously erroneous input to the set command, but what the heck, it was worth a shot since I didn't know my original MAC address. What did I have to lose by trying, I already had the .bk file.

If I now do a

calibrator get nvs_mac /system/etc/firmware/ti-connectivity/wl1271-nvs.bin

(note, that's a get not a set) I get a different MAC address than if I do a

calibrator get nvs_mac /system/etc/firmware/ti-connectivity/wl1271-nvs.bin.bk

(the backup file I made.)

It would appear to me, that if you don't assign a proper address (or per the help even leave out the MAC address completely), it might read the original MAC address from the network card. Or maybe it's just making one up - though I hope not. The help for the calibrator command indicates that the MAC address is an optional argument if I'm reading it correctly:

Usage:	calibrator [options] command
Options:
	--debug		enable netlink debugging
	--version	show version (0.71)
Commands:
...
	set nvs_mac <nvs file> [<mac addr>]

Originally Posted by gadgetman13

I'm not sure that's necessarily completely true. I don't think you need to know the original MAC address.

I blindly issued the command in the above post WITH THE XX:XX:XX:XX:XX:XX left as 'X's. Obviously erroneous input to the set command, but what the heck, it was worth a shot since I didn't know my original MAC address. What did I have to lose by trying, I already had the .bk file.

If I now do a

calibrator get nvs_mac /system/etc/firmware/ti-connectivity/wl1271-nvs.bin

(note, that's a get not a set) I get a different MAC address than if I do a

calibrator get nvs_mac /system/etc/firmware/ti-connectivity/wl1271-nvs.bin.bk

(the backup file I made.)

It would appear to me, that if you don't assign a proper address (or per the help even leave out the MAC address completely), it might read the original MAC address from the network card. Or maybe it's just making one up - though I hope not. The help for the calibrator command indicates that the MAC address is an optional argument if I'm reading it correctly:

Usage:	calibrator [options] command
Options:
	--debug		enable netlink debugging
	--version	show version (0.71)
Commands:
...
	set nvs_mac <nvs file> [<mac addr>]

It will randomly generate a new MAC if one is not set. Here is the original link where I found the info. It appears the hardware does not actually have a burned in address, but is set using calibration utility and stored in nvs file.

http://omappedia.org/wiki/WLAN_Calibration

I used all X's and tapatalk is now fixed for me . Thanks