Database Info

Gio CM7.2 wifi mac address changing after restarting wifi

Hi guys.
I can't reply to original topic, which is here.
I've downloaded version [ROM] CM7.2-20120325-gio-NIGHTLY-AROMA.zip nad installed it without any problems, in newest clockworkmod recovery 5.0.2.7.
My problem is, that after restarting wi-fi or whole system it changes mac address. First 3 pairs (if i remember it's producers code) are still the same, but the rest is random i think.
I've searched through this forum, and user google, but i don't found anything that can help me...
I found how to change mac address, but i read it's not permanent change...
Someone could help me?
Sorry if I added this question to wrong forum, I'm just no so good at english, as you probabky can see while reading my post
OK, sorry that was my fault...
I run app named GooManager and after that and after while it said there is patch to current ROM. I installed this patch (I had to do it manually, because of GooManager crashes, i think it's because of SuperUser, but there were no info about needed priviliges) nad now everything works fine i think
Patch is here. If someone could edit main topic and add this?

[Q] Rom megatron and tethering

First, sorry to post here and no in developpement section but I haven t the right
Second, I try the megatron rom and it was fabulous. Everythings work fine and with guevor kernel, it is very fast.
My problem is that very often, i need to go on web without wifi connection. I do it with my phone ( htc tattoo) via wireless tether. It works fine with stock rom ics rooted but none with megatron.
In this case, the tablet can't see my phone
Any idea to resolve my problem ?

No problem for me, tethering from iPhone4 and Free

Thanks for the answer. Now I know it 's possible. I'll try again. Megatron is really amazing and I hope I can utilise it again

I tried again and same issue. The tf can't see my tattoo when I am with megatron rom. No problem with stock ICS or now with revolver RC2 and guevor kernel 17c.
Anybody have idea why ?
Is it a problem of chanel?
I hope there's a solution because I really prefere megatron but I need the possibility to utilise android tethering

Funny enough, I have the same issue. I love megatron (with guevor's 17c), but wifi tethering from my phone isn't visible to my tf101. It's visible to other people around me, but not to the tf101.

That's weird, mine work fine. I'm actually tethering off my CM7 N1 right now.

I'm happy to see that I'm not the only one with this problem. I'm happiest to see that it's possible tethering work and the phone can be see by the tf. But how?

I have the same problem with Megatron v1.0.4, with Revolution 3.2.2 or stock rom I can make tethering from my computer but I can't in Megatron. I think this is a problem with ad-hoc connections (I have the same problem with cyanogenmod in my phone). I hope it works in Megatron v1.1.0 because I like this rom.

This worked for me.
These are the instructions that came with the file:
1. root is required AND make sure you have your file system app (like Root Explorer) set to make files R/W so you can edit/rename/set permissions
2. turn off wifi
3. go into system/bin and rename wpa_supplicant2 to wpa_supplicant2.bak - that's right folks.. it is NOT wpa_supplicant but wpa_supplicant2 that is running the show
3. download the wpa_supplicant file found here post #24 in my other thread
4. unzip it
5. rename it wpa_supplicant2 NOT wpa_supplicant (already renamed)
6. move it to system/bin and paste it
7. set permissions to 755
8. go back and start up wifi
9. turn on wifi analyzer and you will see (*)AndroidTether with no red Ad Hoc notation!!
10. click to connect
11. surf and tether away!!
On my TF101 I did not have a wpa_supplicant2 in system/bin. I just copied the attached wpa_supplicant2 file into system/bin and set permissions to 755. Now I can connect to ad-hoc wifi signals like from my old Droid-1. The new file does not seem to affect infrastructure connections.
I am not sure under what conditions loading a new ROM will wipe out the modified wpa_supplicant2 file so keep a backup handy.
-Rick

Wireless tethering from mb860 running cm9 to tf101 running megatron. No issues at all.
TF101 Megatron 1.0.4 Guevor test 17c

Updated megatron to 1.1.1 and it works now.
Just make sure you use guevor's kernel from megatron's thread!

In v1.1.1 I see the connection but I can't connect. I tried copying the wpa_supplicant2 file to /system/bin and setting 755 permissions but the same problem. I tried with stock kernel and guevor-17c kernel (downloaded from ricardo's thread)

I'm in the same situation. Nice progress, I'm updated to megatron 1.1.1 with guevor kernel 17c. Now, The tf see my phone and say to me that the signal is strong. But impossible to connect. But at the same time, I can connect my pc to my phone and go to the net.
Where is the mistake?
Any solution welcome
Thanks

I also upgraded to Megatron 1.1.1 and the Adhoc tethering stopped working (with the wpa_supplicant2 file in place.) It was working fine in 1.0.4. When it is working properly your adhoc access point signals will have (*) in front of them. I'll so more testing after I flash back to 1.1.1. -Rick

Nice. I wait and hope you'll find a solution
Regards
Pat

Well, I flashed Megatron 1.1.1. This version only installs a single file: system/bin/wpa_supplicant
With 1.1.1 the adhoc wireless access point (my old Droid-1) shows up in the list and tries to connect (obtaining ip address...) but never connects.
With Megatron 1.0.4 if you copy that special wpa_supplicant2 file I previously posted into system/bin then the adhoc signals show up with a (*) in front of the SSID and you can successfully connect.
I tried installing Megatron 1.1.1 but copied wpa_supplicant from v1.0.4 and the special wpa_supplicant2 into the 1.1.1 rom. Adhoc still would not connect.
So at this time the only way I know to use adhoc tethering with Megatron is with 1.0.4 and copy the special wpa_supplicant2 file I previously posted into system/bin using Root Explorer.
I did these tests with Guevor 17c kernel.
For those who have mentioned that their laptops connect to the wireless access point fine, that's because (at least with windows) the OS can connect to both adhoc and infrastructure mode wifi signals. I believe somewhere starting with ICS the adhoc mode was considered insecure and was removed from the code. Some phones like my old Droid-1 can only create an adhoc tether. I think some of the newer phones can create an infrastructure wifi tether so that explains why some of you are having success.
I am not an expert here so I defer to others who are more learned and experienced than I.
-Rick

I don't use ad-hoc connections but you can try replacing wpa_supplicant in megatron 1.1.2 with wpa_supplicant2.
What i mean is you have to rename wpa_supplicant2 to wpa_supplicant and replace in it in the rom

Hi Ricardo,
Thanks for the GREAT ROM and the great work you do.
After version 1.0.4, replacing wpa_supplicant2 no longer works. I tried it in 1.1.1. The connections show up and try to connect but never actually finish connecting. If I flash back to 1.0.4 and copy the adhoc version of wpa_supplicant2 then adhoc tethering will work again. So something probably changed in the wifi driver after 1.0.4.
Are you saying in 1.1.2 I should delete the existing system/bin/wpa_supplicant, replace it with the adhoc version wpa_supplicant2 (renamed as wpa_supplicant)? I think I tried this in 1.1.1 and wifi would not turn on at all. I will try it again.
Can I do the replacement with Root Explorer on the live system or does the file need to be replaced in the ROM zip file before flashing?
Update: With the adhoc version of wpa_supplicant2 (named as wpa_supplicant) installed on 1.1.2 the wifi does not even turn on. With the original 1.1.2 wpa_supplicant plus the adhoc wpa_supplicant2 in system/bin, adhoc still does not work but the rest of wifi works. Using Guevor's 19.3 now.
-Rick

Thanks also Ricardo for your rom and for all the works and the time you give to answers at our problems.
Thanks to Rick for the help. Just after dinner, I wanted to try your solution with the modifications of Ricardo. You do it before.
Well, wait and hope there's a solution
Pat
Edit
@Rick
I come back to 1.0.4 and make all you said. Everything goes well and know I have tethering. It's the more important for me. I hope a solution will be find with the 1.1.2 but i'm very happy like this.
Thanks a lot
And if somebody find something for 1.1.2 please give us

provide me a logcat in 1.1.2 with the original wpa_supplicant

[Q] XenonHD 4.4.2 - LG P880 aka 4x HD Bluetooth issue

First of all thanks for porting Kitkat to our device! This is a great rom, running smoothly on P880, however, I faced with an issue, which can be a "show stopper" for those who need bluetooth connections. Unfortunately, bluetooth can't be turned on. When I try to activate bluetooth after 4-5 secs returns to off state.
Have you experienced simalar problems? Have you found the root case? Do we have a solution or a workaround? Thanks!

jhevesi said:
First of all thanks for porting Kitkat to our device! This is a great rom, running smoothly on P880, however, I faced with an issue, which can be a "show stopper" for those who need bluetooth connections. Unfortunately, bluetooth can't be turned on. When I try to activate bluetooth after 4-5 secs returns to off state.
Have you experienced simalar problems? Have you found the root case? Do we have a solution or a workaround? Thanks!
Click to expand...
Click to collapse
I've same issue. Any solution? This ROM is very fast but this problem for my use is annoing.
I came from CM11 that i used for almost 1 month. but have many lags same day installed also that have problem with audio on calling and power on display from sleep that require many times to click twice or restart device.
Help please...

FIX thanks to CM11
Hi.
I tried files from latest CM11 build for P880. I have inserted the files into the attachment in this post.
NOTE: THIS ISN'T A FLASHABLE ZIP. EXTRACT AND COPY INTO CORRECT FOLDERS
My work now. Turn on and see devices. I don't had time to test connection but i think is working.
EDIT: I tested for 1 week and use with no problem BLUETOOTH HANDSET and FILE TRANSFER.
There are 7 files.
3 into /system/lib
3 into /system/etc/bluetooth
1 into /system/vendor/lib
I take backup of files, copy on respectively forder and restore permissions
Owner RW
Group R
Other R
I see that don't need reboot but might help
Thanks to CM11

AdrenSnyder said:
Hi.
I tried files from latest CM11 build for P880. I have inserted the files into the attachment in this post.
NOTE: THIS ISN'T A FLASHABLE ZIP. EXTRACT AND COPY INTO CORRECT FOLDERS
My work now. Turn on and see devices. I don't had time to test connection but i think is working.
EDIT: I tested for 1 week and use with no problem BLUETOOTH HANDSET and FILE TRANSFER.
There are 7 files.
3 into /system/lib
3 into /system/etc/bluetooth
1 into /system/vendor/lib
I take backup of files, copy on respectively forder and restore permissions
Owner RW
Group R
Other R
I see that don't need reboot but might help
Thanks to CM11
Click to expand...
Click to collapse
Hi,
Can you please indicate were should i upload those files?
Thanks

Cleophas said:
Hi,
Can you please indicate were should i upload those files?
Thanks
Click to expand...
Click to collapse
Hi there. If you open the zip the files are compressed with the correct path.
however:
/system/etc/bluetooth/
auto_pair_devlist.conf
bt_did.conf
bt_stack.conf
/system/lib
libbluetooth_jni.so
libbt-hci.so
libbt-utils.so
/system/vendor/lib
libbt-vendor.so
I used ROM of 10/02/2014 not the last 27/02/2014. (http://forum.xda-developers.com/showthread.php?t=2639397)
Actually use it like my daily rom with only a problem with tethering not working.

Help with Viper4Android on MTCE_WWW Android 8.0 unit

So I'm trying to get Viper4Android running on my MTCE_WWW Android 8.0 headunit running the stock ROM. I've rooted the system via the adb "injection" method (SuperSU). Root access seems to work fine for everything I've tried.
So then I downloaded the Viper4Andrid files (Viper4Android_FX_v2505.zip) and installed the "Nougat_IO_test_fix.apk" version of the app. I run the app and tell it to load/update the Viper driver - it takes about 30 seconds and says that the driver was installed successfully and tells me to reboot. I reboot the device and try to run Viper4Android, but it goes back to the driver update/install prompt. The actual driver install doesn't seem to be working (even though it says it loaded successfully).
Any idea what I'm doing wrong here?
Thank you in advance!

Ok, I finally got Viper4Andorid working on my MTCE Android 8.0 head-unit... I ended up having to do everything manually (manually editing audio_effects.conf, manually putting the lib4a_fx_ics.so driver file into the proper directory, etc). Since there is no custom recovery available for these MTC? Android head-units, I couldn't just flash any of the flashable V4A .zip files I found online - so I basically did everything a flash would do - just did it manually via a file explorer.
Let me go back and figure out the *exact* steps that I took and then I'll come back here and make sure to document the exact steps I did - may help someone else in the future...
I do realize that I could have just installed one of the custom ROMs that have V4A built in, but they seem to run a lot hotter than stock (from what I've read) and I would rather only install mods that I acutally want to use - instead of installing a bunch of stuff that I will never use and will just make the system run hotter.
So far, from my VERY brief testing, V4A seems to work very well though.

Hello mate, where i can found the steps did you use?

[Guide] Enable VoWiFi on custom ROMs

First attempt at making a guide for this, so please feel free to make suggestions on how to clean it up (I feel like it doesn't lend itself well to step-by-step but you're welcome to try).
Great news everyone! (well, all three of us with T-Mobile/MetroPCS in the USA...)
I got VoWiFi to work last night on a couple custom ROMs and successfully made wifi calls. It doesn't require many pieces, but it can be complicated (not just a step-by-step) to get the required pieces into the right places.
- You need a copy of /system/priv-app/CNEService/CNEService.apk from a stock OOS install (I did it with the one from 9.0.3).
To get that, you might be looking at booting into TWRP with the other slot active or temporarily using something like @mauronofrio's fastboot install ROM from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and just flashing the system image to one slot to grab the file before restoring back to the one you had. Anyway, use caution, be sure of which slot you're on and what you're flashing to, and copy the apk from /system/system/priv-app (the path when you're booted from TWRP instead of inside the active system slot). You'll probably have to use ADB commands to push/pull the file directly to/from a computer if you already have a custom rom installed on one slot with screen lock set up, since /data will likely be encrypted and unavailable when you're booted up in TWRP with the other stock slot active.
- You need to be able to install a rando apk as a privileged system app to get this apk back into /system/priv-app/ correctly on your custom ROM.
There are ways to do this manually that involve lots of permissions and editing XML files for privileged app permissions in a couple places, but realistically you're using a custom ROM so you probably have Magisk (otherwise what the hell are you doing with custom ROMs?) so you should just use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 and pick option 3 to install it. You'll need Magisk, a terminal emulator, and some ability to type a file path to use this module.
- You'll need to make sure that your /system/build.prop file contains the line "persist.vendor.cne.feature=1" (AEX doesn't at first, XenonHD does, not sure about others).
We've got the requisite stuff in /vendor already, this just enables the ability to use it. You'll need to have root access and a file manager/text editor (Amaze is FOSS and available through F-Droid, MixPlorer through XDA Labs is also nice, or use TWRP and a text editor that knows unix line endings on your computer to copy things back & forth via MTP and remember to set permissions after, I think it's chmod 644).
Reboot, unlock, and try to make a test call. Successfully got it to work on AEX & XenonHD last night, I suspect it works for Omni and others as well.
Try some more ROMs out and report back below if it works for you too!

Now if only you could fix the Android Auto bug.
I'm totally kidding. This is awesome. Thank you!

Tested Omni and it works too; just needed the APK added/systemized, already has the correct entry in build.prop.

hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??

Any chance someone could upload and share the CNEService.apk? Would make life a lot easier...

brmbjn said:
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Click to expand...
Click to collapse
If it's not working in OOS, I don't know what to tell you. Might just be that the connection isn't reliable enough for it to decide to enable... but I never used OB10; I switched back to stable 9.0.3 after OB9.

Great work!