Database Info

Wi-Fi MAC address changing

Hello everybody!
I have managed to change the Wi-Fi MAC address of my device and now I share this technique with you. With this method, you can change your address permanently!
What is a MAC address?
A Media Access Control address (MAC address) is a unique identifier assigned to network interfaces for communications on the physical network segment. It may also be known as a burned-in address, an Ethernet hardware address (EHA), hardware address or physical address. (Source: Wikipedia)
Why would somebody change his/her MAC address?
- To access the internet where it is restricted to particular addresses.
- To hide his/her illegal activity. (Though this is not effective enough since the Android system sends product information and a lot of other things to the Google servers and I'm sure that previous IP addresses could be searched for if somebody does something really nasty.)
Is it legal to change the MAC address?
As far as I know, it is. However, I firmly discourage you on doing anything illegal with changed/unchanged MAC.
Let's do it!
What do you need?
- A rooted device.
- A kernel with MAC address changing support. (I include my ICS kernel (version 3.1.10) for those who want to try it out and the method of implementing it into other custom kernels.)
- A file manager that can explore the root filesystem.
How does this exactly work?
Normally, the Wi-Fi driver gets the MAC address from the built-in chip then it writes the address to '/efs/wifi/.mac.info' and '/data/.mac.info'. This is the original burned-in address. This cannot be changed with software modifications, but only by soldering off the chip from the motherboard and rewriting its contents. Our Wi-Fi device is a Broadcom BCM4330. It has very good built-in features and the open source driver can be found in our kernel sources.
There are two different options in the driver (READ_MACADDR and RDWR_MACADDR (actually, there is a WRITE_MACADDR option too, which stands for creating the two files I have mentioned before)), which enable us changing the address. I tested both and found READ_MACADDR better. By enabling it in the kernel, you get some options regarding MAC changing.
Before you change your MAC address in any way, turn off Wi-Fi! I recommend writing down your original address somewhere (just to be extra secured). You can always return to your original one using the second method (read further) or by flashing a kernel that doesn't have the patch.
- If you flash a patched kernel and delete the '/efs/wifi/.mac.info' file, the driver will generate (!!) a custom MAC address based on some predefined rules (The first 24 bits are common in all generated addresses.).
- Of course you can set your own custom MAC address. Do this by editing the '/efs/wifi/.mac.info' file with a file manager. If you change it to an incorrect address, the system will automatically use the original (burned-in) MAC.
For kernel developers who want to enable this:
Find '#define WRITE_MACADDR' after '#ifdef CONFIG_MACH_N1' in 'drivers/net/wireless/bcmdhd/src/dhd/sys/dhd_sec_feature.h' and insert '#define READ_MACADDR' after that line. This is for ICS kernels (version 3.1.10), but the patch must work on GB ones too. You just have to insert the define somewhere else (I didn't look into this.).
(I count on you guys in implementing this! )
I attach my prebuilt (secure, MMC_ERASE_CAP disabled) kernel for trying out this feature. It is an ICS kernel (version 3.1.10).
Every custom modification to devices have risks. Use this at your own risk!
Have fun and enjoy!

Thanks!
Just tried patching the kernel, it works! So, this feature will be included in my next kernel.
Before flashing the patched kernel, when I turn off wifi, delete .mac.info file, re-enable wifi, the MAC address is not changed.
However, after flashing the patched kernel, after I turn off wifi, delete .mac.info file and re-enable wifi, the MAC address is changed!
Thanks very much for the useful guideline from Adam77Root :good:

Hey bro can u explain this in a more simpler manner...I'm a newbie here and i need this! bcuz my brother alwayz blocks my wifi mac address so i cannot access wifi. I hav a rooted Samsung galaxy ace s5830 using cm 10.1 rc4......thanks in advance!:good:

Abuzzz said:
Hey bro can u explain this in a more simpler manner...I'm a newbie here and i need this! bcuz my brother alwayz blocks my wifi mac address so i cannot access wifi. I hav a rooted Samsung galaxy ace s5830 using cm 10.1 rc4......thanks in advance!:good:
Click to expand...
Click to collapse
If kernel supports only we change the WIFI MAC Address, we can not use it on all the kernels...

Hello,
Is it possible on Samsung Galaxy SII GT-I9100 ?
thanks

miradorid said:
Hello,
Is it possible on Samsung Galaxy SII GT-I9100 ?
thanks
Click to expand...
Click to collapse
Just have taken a look into your kernel sources and it seems it is.
Check this thread: http://forum.xda-developers.com/showthread.php?p=37299543
Somebody will surely compile a kernel for you.

thanks ! I hope anyone will do this

Is it possible to port this to nexus 7 wifi edition with Dirty Aokp rom?
I already have this on my r with cm10.1 kernel
Sent from my GT-I9103 using Tapatalk 2

Deadfreak said:
Is it possible to port this to nexus 7 wifi edition with Dirty Aokp rom?
I already have this on my r with cm10.1 kernel
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
I have looked into the sources of your Wi-Fi driver (the same BCMDHD) and it seems it doesn't support it. Maybe this is a Samsung-only feature.

any suggestion...?
mj.vikram said:
If kernel supports only we change the WIFI MAC Address, we can not use it on all the kernels...
Click to expand...
Click to collapse
Can you suggest me a ROM with the suitable kernel to change the mac address of my Samsung Galaxy Ace S5830 please?? It would be of great help...

Abuzzz said:
Can you suggest me a ROM with the suitable kernel to change the mac address of my Samsung Galaxy Ace S5830 please?? It would be of great help...
Click to expand...
Click to collapse
I think your best bet would be the galaxy ace forums. You could search if there's an existing kernel with this functionality or else you could direct one of the kernel developers there to have a look at this thread.

I'm a beginner, plz explain in detail such that I can do it.
I'm using Karbonn A11(rooted).
I need to change my Wi Fi mac address because my network administrator blocked my device mac address.
yo be able to connect to wi fi I need to change my wi fi MAC address...
plzz help me..
plzzz
---------- Post added at 02:42 PM ---------- Previous post was at 02:20 PM ----------
I'm using Karbonn A11(rooted).
I need to change my Wi Fi mac address because my network administrator blocked my device mac address.
yo be able to connect to wi fi I need to change my wi fi MAC address...
plzz help me..
plzzz

You need a kernel that supports it.
BTW: Why on earth is this thread in the Q&A??

Adam77Root said:
You need a kernel that supports it.
BTW: Why on earth is this thread in the Q&A??
Click to expand...
Click to collapse
OK then asked mod to move this one to General Forum.

hmm, good idea . but not for all mobiles, I think.
not working for N7100.
thanks anyway.

CracKey said:
hmm, good idea . but not for all mobiles, I think.
not working for N7100.
thanks anyway.
Click to expand...
Click to collapse
If you didn't say, I would have tried it out on my refrigerator.

...not on my refrigerator, but on my U8860
Adam77Root said:
If you didn't say, I would have tried it out on my refrigerator.
Click to expand...
Click to collapse
Hello experts,
since a long time I'm trying to fix my mutating MAC on a Huawei U8860 (so called Honor).
Your Thread gives me new hope. Atm I'm running a custom rom (baidu v.5, ROM 43) on my device.
Do you think, it's possible to insert the phrase into the kernel-source to make the MAC fix again? The wlan-chip is nearly the same as in your tested device (bcm4329).
What else do I have to patch? Is it necessary to write the MAC (seen on the label under battery) into any config-file?
I apprecheate your help - thanx for reading...

Works on Samsung S4 mini with CM 11, however I need to reboot after changing .mac.cob even when deleting .mac.info (which does not automaticly returns), as turning off/on WiFi isn't enough.
I guess the READ_MACADDR option is missing, and at one point I'd like to make my own CM modification. Or is there a more simple solution?

I'm new here..
I have rooted my galaxy note 2 gt-N7100
I want to change my mac address to another one that i want
Can you tell me how can I do it?

Hi,
Just over a year ago, I asked you a solution for my Galaxy S2, and you found me a solution thanks to this post on the Galaxy S2 forum.
Is there a similar kernel for Galaxy S4 GT-I9505 ?

[APP][2.2+] DriveDroid - host ISO/IMG files to boot your PC from

DriveDroid allows you to boot your PC from ISO/IMG files stored on your phone. This is ideal for trying Linux distributions or always having a rescue-system on the go... without the need to burn different CDs or USB pendrives. The paid version of DriveDroid does not include ads and helps the developer.
DriveDroid also includes a convenient download menu where you can download USB-images of a number of operating systems from your phone.
You can also create USB-images which allows you to have a blank USB-drive where you can store files in. Another possibility is to use tools on your PC to make a bootable USB-drive out of the blank image that DriveDroid created.
DriveDroid (free)
DriveDroid (paid)
Website
Changelog and downloads
List of distributions available in DriveDroid
Donate
IRC (#drivedroid on chat.freenode.net)
Beta
To participate in the beta join the Google Group here: https://groups.google.com/d/forum/drivedroid
After that join the beta of either DriveDroid (Free) or DriveDroid (Paid)
Distrowatch image repository
If you are missing a certain distribution or want more images available in the download list, you can add download repositories. At the moment I have made a repository for Distrowatch. These images are not officially supported, so they might not work for CD or USB booting.
Go to DriveDroids preferences, under "Image repositories" and add the following URL: http://softwarebakery.com/apps/drivedroid/repositories/distrowatch.json
USB Mass Storage (UMS)
DriveDroid relies on the kernel of Android, in particular the USB Mass Storage (UMS) feature. It allows your phone to act as an USB-drive and have a device (SDcard) or file (ISO/IMG) be used as the content for that emulated drive.
Different Android devices implement this feature differently. Most modern devices do not have UMS enabled by default, but it is supported by the kernel. I've added a option to DriveDroid to change the USB-mode for devices that do not support UMS by default, but no guarantees. I'm getting very mixed reports of devices working and not.
I need all the help I can get to fix this problem. Hopefully we can figure out some method to enable UMS in a stable way.
Hybrid-ISOs
Since most phones only support emulating USB-drives, DriveDroid will not act as an CD-drive. This means that not all ISO files will work, only hybrid-ISOs and IMG files. Hybrid-ISOs are specially crafted ISOs that is used on many modern Linux-distributions. DriveDroids downloadlist contains most of the distributions I've found that do have hybrid-ISOs.
This is just to notify you that you have to convert non-hybrid ISOs by writing the ISO to the emulated USB-drive. You can get a blank emulated USB-drive by creating a blank image through DriveDroids + menu.
Tutorials
Since some popular uses are not available out-of-the-box, I've written a few tutorials on my website that handle some of those uses:
Using Rufus to burn any ISO to DriveDroid *Recommended*
Windows installation on DriveDroid
Install Hirens Boot CD on DriveDroid (download the pre-built Hirens Boot CD image here)
Shrinking images on Linux to save space on your phone
USB-drive and CD-drive emulation
These two modes allow your phone to act as an USB-drive or as an CD-drive. Most devices only support USB-drive emulation. Some devices only support CD-drive emulation. To get both USB-drive as well as CD-drive emulation on your phone you need a patched kernel (see below).
With USB-drive emulation it is possible to boot IMG files and most Linux-based ISO. It also allows you to write to the disk, which allows you to create data-disks as well as install an OS onto the USB drive. The downside of this mode is that some ISOs will not boot, since those ISOs are created for CD-drives.
With CD-rom emulation it is possible to boot all CD-based ISOs.
So, having both USB-drive emulation as well as CD-rom emulation is preferable.
Some roms with a range of supported devices have patch reviewing systems in place where I periodically submit patches to new devices. You can check what kernels have the right patches in their patch review system. To know which kernel your device is using, check out this list to see kernels are used by what devices.
CyanogenMod: supported kernels
SlimRoms: supported kernels
CarbonROM: supported kernels
aicp-rom: supported kernels
Nameless-ROM: supported kernels
Other custom kernels that have the right CD-rom patches applied are:
Dorimanx Kernel 8.33 on stock and AOSP/CM roms for the Samsung Galaxy S II (I9100)
Dorimanx Kernel 9.33 on AOSP/CM roms for the Samsung Galaxy S II (I9100)
CyanCore Kernel v2.8.6 by ts1506 for the Samsung Galaxy S (I9000)
BMS Kernel by GideonX for Samsung Galaxy S3 Sprint (d2spr)
BMS Kernel by GideonX for Samsung Galaxy S3 AT&T (d2att)
BMS Kernel by GideonX for Samsung Galaxy S3 Verizon (d2vzw/d2usc)
Patched stock kernel by porear for Samsung Galaxy S3 T-Mobile
GearKernel 1.0.4 and higher for Samsung Captivate
GearKernel 1.0.4 and higher for Samsung Galaxy S i9000 and i9000B
GearKernel 1.0.4 and higher for Samsung Vibrant
DooMKernel for Xperia Z
DooMKernel for Xperia Z1
Devil2 kernel for Samsung Galaxy Note 2 (GT-N7100)
X-NOTE Leonardo Edition for Samsung Galaxy Note 3 (N9005)
ThunderZap for Xperia L
ShinTo for Samsung Galaxy Note 3
Unofficial CyanogenMod-compatible Galaxy Note 3 kernel by unic09
Basel kernel (stock) for Samsung S Duos (s7562) by baselsayeh
AEL kernel for Samsung Note 3 by friedrich420
FIRE-ICE kernel for Nexus 9 by USBhost
ElementalX for Nexus 5 (hammerhead)
Kangaroo Kernel for HTC One
WR-Kernel for Wiko Rainbow
Unikernel for Samsung Galaxy S6/S6 Edge
CleanSlate for HTC 10
If this list is missing any rom/kernel that has the feature, please contact me.
If your favorite kernel is not supporting this feature, direct the kernel developer to this section.
If you know your way around kernel code and patching, you can get the patches here:
Patch to allow applications (like DriveDroid) to switch between USB and CD-mode
Patch to fix booting from the emulated CD-rom drive (only needed for Android 2.x kernels)

[post for future use]

Hi,
Now there's a dedicated topic. :good: The place to give a bit of feed-back.
As I already said there, congrats for this idea and most of all, well made and user friendly. Thanks, mate.
It worked with no problem with the Samsung GS3 i9300 on WanamLite JB MB5 v6.2 with Wanam's Adam kernel v1.2 (I don't really know what Wanam cooked there but it works fine) that is MTP/PTP. Note that when DriveDroid's UMS is enabled, both check-boxes in the regular S3 USB panel have no marks (can normaly have only one checked, never none unchecked).
Other people may please confirm if it works on Galaxy S3 i9300 with stock or other custom kernels.
Less surprisingly, it works fine with Samsung GS2 i9100 on (WanamLite JB LSE v14.3) since it always had Mass Storage Transfer, afaik (but I'm not sure), actually on Wanam's v14.3 it has.
Working on pure CD format (like Daemon Tools for Windows or any Virtual CD mount system) would be top notch —TonyHoyle has cooked a kernel patch to enable virtual CD support, there's an idea to dig, Apple dmg should follow.
But for the moment with what is given, creating own disc ISO to fill with whatever you need later on a computer, is really fine. Polishing the angle to reach v1.0.

I've always wanted to do this. Thank you.
Sent from my MB860 using xda premium

Awesome, just awesome freaking app!!!!!!!!¡!!!!!!!!!!!!!
Sent from my Nexus 4 using xda app-developers app

Hi, again i have 3 questions id like to así:
-is there any test i can do todo verify if a ISO file is compatible?
-what method por spp do you use todo make a compatible file from an ISO format not supported?
-how can check if cdrom feature is working?
Great work!
Enviado desde mi GT-I9000B usando Tapatalk 2

CD-Rom Support in Existing Kernels
Hi,
I'm using this on my Samsung Galaxy S3 using Omega Rom 43.x and the USB Drive support works great, once I turned off USB Debugging.
Does anyone know if any of the current Kernels for the Samsung Galaxy S3 have the required patches for the CD-rom support as I would also like to boot a couple of CD's from my phone.
Thanks
Kevin.

FrozenCow. does your app now support Note II fully?

Any how tos. I tried. But it's not working. Not complaining. The app is fine. I know I'm doing something wrong. Any help is appreciated thanks
EDIT:
Got it working. Awesome work dev. Here's a small step by step instructions for those who were noobs like me.
Download slitaz from within the app
Select slitaz iso.
Select S3C1 and F Mass Storage 1
Also enable Usb storage.
Disable ADB (Android Debugging)
Reboot system.
Do the thing with your boot procedure.
And voila, (I hope)
Thanks a lot dev. This really made my day. Keep rocking. All the best for this app. I will follow it closely :thumbup:
EDIT 2: Btw my device S2 9100 on Alliance ROM 7.02
Sent from my GT-I9100 using Tapatalk 2

diosemperador said:
-is there any test i can do todo verify if a ISO file is compatible?
Click to expand...
Click to collapse
Yes, check whether the image has a partition table usually gives a very accurate indication that the disk is hybrid. To do this (under Linux) use the command:
Code:
$ fdisk -l myimage.iso
It'll show some info about the disk, but also a partition (usually that partition is marked as being NTFS/FAT, but I think that is part of the trick to make it work on both CD and disk). If it shows no partitions at all you know it probably isn't a hybrid disk.
diosemperador said:
-what method por spp do you use todo make a compatible file from an ISO format not supported?
Click to expand...
Click to collapse
For Linux distributions that are build on a recent version on syslinux you can use the tool 'isohybrid' like this:
Code:
$ isohybrid myimage.iso
It'll convert the iso so that it is hybrid. For all other ISOs (that are not build on syslinux) you can you the methods described for that OS to burn it to a USB drive. First create an image in DriveDroid, select the image so that it shows up on your PC as a USB disk, next use the OS-specific tools to burn the iso to the (emulated) disk. It'll be stored on the IMG you made.
You can try this on the official ISO of SliTaz 4 (so not the image form DriveDroids downloadlist). The devs forgot to make version 4 of their OS hybrid, but it does rely on syslinux, so it's possible to convert it using isohybrid. I've done this and put the converted ISO on my server, so that the hybrid-ISO is available in the downloadlist (I've only done this for SliTaz because it is so small and awesome).
If you see that a distro is convertable with isohybrid you should contact those devs. Some of them do not realize that this option is available or what the advantage is. When they distribute their ISO as a hybrid one I can put their distro on DriveDroids downloadlist too.
diosemperador said:
-how can check if cdrom feature is working?
Click to expand...
Click to collapse
Ah, well, DriveDroid should show a CD icon next to the USB and locked-USB icons when selecting an image. At the moment only CyanogenMod nightly builds for the i9000 (kernel is named android_kernel_samsung_aries)
diosemperador said:
Great work!
Click to expand...
Click to collapse
Thanks!
kjtaylor13 said:
Does anyone know if any of the current Kernels for the Samsung Galaxy S3 have the required patches for the CD-rom support as I would also like to boot a couple of CD's from my phone.
Click to expand...
Click to collapse
Question to all: if you have applied the patches on their kernel, please post it here so others can try it. As far as I know no-one has put such a kernel/rom online yet, except for CyanogenMod nightly for the Samsung Galaxy S.
arunreturns said:
Got it working. Awesome work dev. Here's a small step by step instructions for those who were noobs like me.
Download slitaz from within the app
Select slitaz iso.
Select S3C1 and F Mass Storage 1
Also enable Usb storage.
Reboot system.
Do the thing with your boot procedure.
And voila, (I hope)
Click to expand...
Click to collapse
Add "Disable ADB (Android Debugging)" to those instructions. It seems that's the final thing I need to add to DriveDroid to make it work for a lot of people. I've had several reports some Nexus devices stopped working because I fixed DriveDroid to allow ADB (previous versions just disabled ADB without consent). Some devices work with ADB running too (like my phone), but some just won't boot (although they do show up as USB devices on their OS).

Thanks
Thanks
Thanks
Ans one more petition , is there anyone kind enough to ask to derteufel the dev on this thread [ROM] Helly_Bean [4.2.2] [nightly builds] -i9000B at website now! ( http://forum.xda-developers.com/showthread.php?t=2012061
) to add the patch for cdrom on his kernel, i would do it my self but i cant post on devs section
Thanks
Enviado desde mi GT-I9000B usando Tapatalk 2

Frozen,
Thank you for the app! I always felt my phone should be able to replace the USB sticks I have laying around. I saw the article on Lifehacker about DriveDroid and had to have it. And while I've been unsuccessful getting it to work on my GNex or my OG Droid, I've still purchased the app because of the way you're handling yourself on the forums. You're responsive, friendly, and I hope you can continue to be so when your app explodes in popularity even further. :good:
And it always helps having assistance from the XDA community.
Edit: It may also be debugging is my problem since that's on both of my phones and I just now read that could be causing issues.

diosemperador said:
Thanks
Thanks
Thanks
Click to expand...
Click to collapse
Thanks!
diosemperador said:
Ans one more petition , is there anyone kind enough to ask to derteufel the dev on this thread [ROM] Helly_Bean [4.2.2] [nightly builds] -i9000B at website now! ( http://forum.xda-developers.com/showthread.php?t=2012061
) to add the patch for cdrom on his kernel, i would do it my self but i cant post on devs section
Click to expand...
Click to collapse
I've done a post there. We'll see what happens.
HelixtheII said:
Thank you for the app! I always felt my phone should be able to replace the USB sticks I have laying around. I saw the article on Lifehacker about DriveDroid and had to have it. And while I've been unsuccessful getting it to work on my GNex or my OG Droid, I've still purchased the app because of the way you're handling yourself on the forums. You're responsive, friendly, and I hope you can continue to be so when your app explodes in popularity even further. :good:
Click to expand...
Click to collapse
It's too bad it's not working for everyone yet, but I'm pretty confident the next version will work for a lot of people.
HelixtheII said:
And it always helps having assistance from the XDA community.
Click to expand...
Click to collapse
Yes indeed, that was the main purpose of this thread + to focus discussion more. Email works too for a bit, but it's becoming hard to keep up :-/.

FrozenCow said:
Thanks!
I've done a post there. We'll see what happens.
Click to expand...
Click to collapse
Thanks again , just came from there and the dev already confirm that he has merged your patch in the kernel for future updates !
Enviado desde mi GT-I9000B usando Tapatalk 2

diosemperador said:
Thanks again , just came from there and the dev already confirm that he has merged your patch in the kernel for future updates !
Click to expand...
Click to collapse
Hah, indeed I see. Cool to see that it already was in there. I guess more rom-devs use CyanogenMod's patches. Now we'll just have to wait for a release so that more people will be able to use the CDrom feature and we'll have some more real-world testing.

Wow, this is sick... I hope I will be able to test that soon!
Really a cool idea!
Continu the good work!!!
[EDIT]
SliTaz boot on S5830d running firekernel and CM7based rom... will probably try to convert an WinPE to hybrid tomorrow at work and test... But omg I want to get my sgs back for real iso
Do you think your patch can be apply to CM7 kernel ? If its the case I may post in few thread.....
[EDIT2]
WinPE in 2 minutes..cool.. build the file is even faster than burning a cd. That procedure on your website is very usefull as a guideline

Hi,
I've forked and patched boeffla's kernel for GS3 compiled and now I can boot CD's and USB sticks from my phone. Not bad for my first attempt with a kernel.
Being new to github how do I post the patches for boeffla to merge with his kernel? As his kernel is based on Samsung Stock Kernel, is there a Github somewhere that all GS3 Dev's use that I could post the patches too?
I'll post an odin tar file for anyone who wants to try it when I get into work later.
Edit: And Heres the Link http://goo.gl/la909
Thanks Frozen for a great app.
Kevin
Sent from my GT-I9300 using Tapatalk 2

Silentbob999 said:
SliTaz boot on S5830d running firekernel and CM7based rom... will probably try to convert an WinPE to hybrid tomorrow at work and test... But omg I want to get my sgs back for real iso
Do you think your patch can be apply to CM7 kernel ? If its the case I may post in few thread.....
Click to expand...
Click to collapse
I think it's possible to apply the patch to CM7 as-is (without conflicts), but I don't know for sure. The changes aren't that big and are applied to kernel code that shouldn't be changed much. However some device manufacturers do think it's needed to change the code in there, so I can never be sure .
Silentbob999 said:
WinPE in 2 minutes..cool.. build the file is even faster than burning a cd. That procedure on your website is very usefull as a guideline
Click to expand...
Click to collapse
nice! Good to hear the procedure is helping people. I need to do a post about UEFI too, could be useful too.
kjtaylor13 said:
Hi,
I've forked and patched boeffla's kernel for GS3 compiled and now I can boot CD's and USB sticks from my phone. Not bad for my first attempt with a kernel.
Being new to github how do I post the patches for boeffla to merge with his kernel? As his kernel is based on Samsung Stock Kernel, is there a
Github somewhere that all GS3 Dev's use that I could post the patches too?
Click to expand...
Click to collapse
Nice job. Well, I've been looking for something like this too. But I think Samsung just 'publishes' their kernel source as tars somewhere. No way to have input it seems. Where you want to apply this patch is at boeffla, CyanogenMod or Google. Since Samsung is basing their kernel on Google's (at least I think so), I think the ultimate goal is to let the patches be accepted by Google. I've looked at the process of doing this, but it involves quite some people. I first want to make sure these patches are tested on a number of devices (by applying the patches to popular custom roms first).
Anyway, Boeffla's account is available here: https://github.com/andip71
Fork one of his kernels (I'm not sure which one you're using), so that you have your own repository of his code. Now you can pull from your repository, apply the patch, commit and push to your repository (with git). Once pushed you can do a 'pull request' through github on the webpage of your repository. Github has quite a lot of information about how to do things here: https://help.github.com/
If you need help, feel free to ask or join me on IRC.

Hi kjtaylor13,
Thanks for the work. Witch Boeffla's version did you patched?
I'm used to run stock kernel or since his last firmware update, Wanam's Adam kernel that runs fine, except the author is not eager to mod the kernel too much --in his perspective to give us John "half-geek" Doe the best without too many settings hassle, it's perfectly understandable.
But this idea of hosting and launching real ISO is very exciting.

FrozenCow;
Anyway said:
https://github.com/andip71[/url]
Fork one of his kernels (I'm not sure which one you're using), so that you have your own repository of his code. Now you can pull from your repository, apply the patch, commit and push to your repository (with git). Once pushed you can do a 'pull request' through github on the webpage of your repository. Github has quite a lot of information about how to do things here: https://help.github.com/
If you need help, feel free to ask or join me on IRC.
Click to expand...
Click to collapse
Thanks, did a pull request on github so just waiting to see if it's accepted.
Zoot Allures said:
Hi kjtaylor13,
Thanks for the work. Witch Boeffla's version did you patched?
Click to expand...
Click to collapse
I used the latest kernel from his website / github, it was 2.9 I was already using it as my kernel.

[APP][5.0+][ROOT] Change Operator Name (root)

This is the support thread for my paid app "Change Operator Name (root)".
With this app you can change the displayed name of the network operator (brand). The app is available on Google Play.
Feel free to post questions, suggestions, bug reports, etc. here.
Device compatibility: second post
Requirements: On Android 5.0, when SELinux is set to enforcing: a superuser app with support for a SELinux context parameter (-cn). Currently, only SuperSU supports this parameter.

Device compatibility:
Please note: This is not an exhaustive list and only mirrors my current state of knowledge. If your device is neither listed in the "compatible" or "incompatible" list its compatibility isn't known yet. If you test it please report and I'll update the lists.
Compatible:
Nexus 5
Incompatible:
(none known yet)

(reserved2)

To everyone who bought the app on Google Play: Thanks for your support! If you can spare a minute, please consider giving it a review on Google Play - it will help in increasing the app's visibility.

cygery said:
(reserved)Device compatibility:
Please note: This is not an exhaustive list and only mirrors my current state of knowledge. If your device is neither listed in the "compatible" or "incompatible" list its compatibility isn't known yet. If you test it please report and I'll update the lists.
Compatible:
Nexus 5
Incompatible:
(none known yet)
Click to expand...
Click to collapse
Can you make it compatible with kitkat ?

VoLTaqe said:
Can you make it compatible with kitkat ?
Click to expand...
Click to collapse
Most likely not. The method I use was introduced in Lollipop and I'm not aware of a similar method with the same comfort on previous versions. Won't your device receive an update to Android 5.0?

There shouldn't be any issues with this app on Android 5.1, however, if anybody experiences issues please post.

cygery said:
There shouldn't be any issues with this app on Android 5.1, however, if anybody experiences issues please post.
Click to expand...
Click to collapse
After a more in depth check this turns out to be wrong. I'm unable to get the app working on Android 5.1 at this time. Once I find a solution I'll post again.

Still no success with Android 6.0 (or 5.1).

[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...

[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...
unfortunetely it only works with some qualcom based devices, you can find a list of working devices under:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
new version is out: 0.9.3
Version 0.9.3
Support Android 5
Fix initialization issue on newer devices
Translation to German and Dutch
Click to expand...
Click to collapse
SnoopSnitch is an Android app that collects and analyzes mobile radio data to make you aware of your mobile network security and to warn
you about threats like fake base stations (IMSI catchers), user tracking and over-the-air updates. With SnoopSnitch you can use the data collected in the GSM Security Map at gsmmap.org and contribute your own data to GSM Map.
This application currently only works on Android phones with a Qualcomm chipset and a stock Android ROM. It requires root priviliges to capture mobile network data.
Requirements:
Qualcomm-based Android phone (see list below)
Stock Android ROM, version 4.1 or later
Note: Unfortunately, custom Android ROMs like CyanogenMod are not supported, as they lack the drivers necessary to collect radio data.
Root privileges on phone
Tested Devices:
The following devices have been verified to work:
Samsung S3 Neo (GT-I9301I)
LG G2 (LG-D802)
Sony Xperia Z1 (C6903)
Samsung S5 (SM-G900F)
Motorola Moto E (Moto E)
Samsung S4 (Qualcomm variant)
It is very likely that other Qualcomm-based Android phones also work, if they are rooted and have a stock firmware.
Incompatible Devices:
The following devices have been found to be incompatible and can not be used with SnoopSnitch:
UNSUPPORTED: Every device without a Qualcomm chipset
UNSUPPORTED: Every device with custom ROM
UNSUPPORTED: Samsung Galaxy S2 & S3
UNSUPPORTED: Nexus 5
UNSUPPORTED: Huawei Ascend Y300
Click to expand...
Click to collapse
from https://opensource.srlabs.de/projects/snoopsnitch (project site)
or google play link:
https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch

Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?

geminga said:
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
Click to expand...
Click to collapse
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.

xd.bx said:
About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Well, Carsten Nohl, one of the developers, said yesterday on 31C3, that on CustomROMS like CM certain proprietary drivers are missing, which are needed for getting certain debugging information. Later yesterday in a workshop on 31C3 participants found out, that on some CM11 Phones the app is working.
There the app worked on:
Samsung S3 Neo
Samsung S5
LG G2
Sony Xperia Z1
Motorola Moto E
and dind't work on
Samsung S2, S3, S4 and S5 Exynos
Nexus 5
Fairphone
you can watch the presentation from Nohl on 31C3 here:
http://media.ccc.de/browse/congress...830_-_mobile_self-defense_-_karsten_nohl.html
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"

About the compatible devices - I can confirm the app works on on Xperia V with the stock 4.3 Android. It gives no errors, but I have not yet encountered malicious GSM cells to verify the detection works ok.

Why do we have to make long distance calls and send sms to use this app?

http://forum.xda-developers.com/showthread.php?t=1422969

Celestial Fury said:
Why do we have to make long distance calls and send sms to use this app?
Click to expand...
Click to collapse
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.

rudolfm said:
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
Click to expand...
Click to collapse
Sure I did. It doesn't say why we have to call/sms a specific number and why we data can't be gathered from our every day call/sms and why data can't be sent to the test site through the internet rather than call/sms.

XsheldorX said:
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
Click to expand...
Click to collapse
You need to flash a compatible kernel. http://d-h.st/mmb

Works on my SONY Xperia Z1 with CM11.
Though, when doing the test call my device was banned, for whatever reason....

Yeah I can (probably) confirm this with Z1 compact with CM 11. Works since day one I guess. The test works (around the first days incoming calls and sms did not, probably because of overload of the callingserver), but never had any sort of attacks. Now I'm in doubt if radio-part does not work with cm 11, as mentioned in the description, or there were zero attacks.
Another thing I observed. The software sometimes produces many wake-locks. But I guess thats normal if backgroundservice is active.
@ papperlapapp: Did you monitor any attacks (SS7 or silent sms)? Or even IMSI-catchers?

Installed the app without problems on my S5 with Phoenix ROM (Stock Based). However, when I start the active test, the app stops responding and android asks me several times if I want to close it. I chose no every time. Now I'm wondering if the tests are still running in the background or if the app just hang. Started the tests about 35 min ago, still waiting, absoluteley nothing happened yet.

Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring

Works on Samsung Note 3 SM-N9005
Sent fra min SM-N9005 via Tapatalk

xperia E1 seemingly working
E1 seems to work.
but now what ? where are the logfiles where I see stuff live?
google 31c3 "mobile self defense" for the thrilling background story
let's all hope the CCC talkers have learnt better English by 2016 (Mr Nohl being one of the best still) !
https://media.ccc.de/browse/congres...self-defense_-_karsten_nohl.html#video&t=3838

xd.bx said:
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2

MForce22 said:
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
Click to expand...
Click to collapse
I don't know. Just try, at worst you'll have to reflash the old kernel back.

itman-ch said:
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Click to expand...
Click to collapse
it is on play store too ^^

srlabs posted a device list:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
and a new version is out:
Version history
Version 0.9.2
Fixed app lock-up issues
Improved device compatibility check
Handled unsupported LTE gracefully
Version 0.9.1
Fix problem where SnoopSnitch would leave the phone muted after a test
Remove issue with disappearing (Skype) dialing dialogs
Resolved performance issue in analysis
Version 0.9.0
Initial public release
Click to expand...
Click to collapse

[Module][Development] Double Tap to Wake v2.0 [Guide too]

Hi fellow xda members!
I'd like to share with you something that I had been very curious about.
Well if the title hasn't already given it away, it's the generic version of Double Tap to Wake (for almost all devices)
And what's different is that I've studied, refactored and restructured the code myself to be more efficient, faster, and shorter.
As a result, I've decided to bump this good ol' kernel module to V2.0
First of all, huge thanks and respect to Dennis Rassmann who gave us the original dt2w v1.0 kernel module (for almost all devices)
Here's the precise changes :
1) Restructure (and rewrote parts) dt2w main function code.
2) Remove useless variables. It is possible to achieve the same thing with less space.
3) Rewrite the distance formula. Change it from rectangular linear to circular radial.
4) Remove unnecessary checks which are either always true or never reached.
5) Reduce space and time complexity for the algorithm.
6) Use vibrator call method AFTER queuing the pwr_on so that there is no delay between calling the vibrator and the power button emulation.
(Step 6 explained : Calling power method before vibrator is a UX tweak. When we call power method first, it queues the power command to the sched (or so I think what queue does) and we know the screen doesn't wake up immediately. So, while the screen is in the mid of waking, we next run the vibrator method. This causes the vibrator to react after the screen on is triggered, and that creates a feeling of spontaneity that the vibrator is running while the screen is turning on. In version 1, the vibrator starts vibrating before the display is even queued. This feels like it takes longer (although it doesn't, it's just a UX placebo))
Click to expand...
Click to collapse
Result : Final dt2w main function is about half the length of earlier one, and more effective.
Here is the source for DT2W v2.0 - https://github.com/tanish2k09/Doubletap2wake-2.0
Guide about how to add it :
---It's all already written in the README.md in github, it's better to check that instead---
Code:
Follow these steps if you have the good ol' v1.0 from dev Dennis Rassmann :
(For feasibility, I've added port-dt2w-functions.txt with all the necessary code)
(Also note : doubletap2wake.c has been referenced as dt2w.c just because I'm too lazy)
1) Replace the whole "detect_doubletap2wake" function from v2.0 to v1.0
2) Remove "calc_feather" function from v1.0 and place "calc_within_range" function from v2.0
3) Define "DT2W_RADIUS" in the beginning of dt2w.c, along with other defines. Copy from port txt.
4) Remove "DT2W_FEATHER" definition from the defines.
Optional step 5: Change Version, author, desc, etc. Find "/* Version, author, desc, etc */" and replace next 4 lines from port file.
6) Remove the third argument from all "detect_doubletap2wake" calls. Usually it's "true"
7) That's it! You're good to compile it now.
8) If it works nicely, make sure to give me a thanks on xda thread :D
Follow these steps if you don't even have the good ol' v1.0 from dev Dennis Rassmann :
1) Get dt2w-v1.0 by Dennis Rassmann and compile it successfully first.
2) Follow the steps in above part.

Note for mods :
In case you find this thread to be in the wrong subforum, please move it to the right section while informing me.
In case you find anything inappropriate according to xda forum rules, please contact me before taking any actions so I have a chance to correct any and all mistakes I might have commited.
I see @xanthrax is a forum moderator here. Please be kind enough to review the thread.
Edit : xanthrax moved the thread to appropriate subforum already and reviewed the thread and confirmed nothing wrong here.

It's available for Redmi Note 3 MTK?

GreatStorm said:
It's available for Redmi Note 3 MTK?
Click to expand...
Click to collapse
This is a general module.
The steps I have provided will work for all mtk phones.
Just ask any of your experienced kernel developers (or you yourself, if you're one of the Devs) to check my thread (and the GitHub source readme) to add it.
If you already have dt2w, this will work 100%
Feel free to contact me for any doubts. :laugh:
In some time I'll also post trace2sleep (or t2s) module.

any link for dt2w v1.0 kernel module ?

sougata7684 said:
any link for dt2w v1.0 kernel module ?
Click to expand...
Click to collapse
Unfortunately you'll have to search for GitHub commits "add dt2w".
I couldn't find a generic all-driver file itself, so you need to find the one with your driver.

ChinmayDalal said:
I saw some commits on GitHub on 3.10.xx kernels, but my device's dev told me that he already tried porting from 3.10.xx kernels.
He needs 3.18.xx kernels to port.
(MT6737)
Click to expand...
Click to collapse
This thread is just for dt2w module.
The device must have a working touch panel support for gestures before adding v2

module working on Samsung phones
Does this module work on any Samsung phones? I've got an s7 running Nougat via "The Galaxy Project" rom, the SuperKernel, and i'd really like this feature. The processor is an exynos8890.
I'd love to have this feature, miss it from my old g2.

tech927 said:
Does this module work on any Samsung phones? I've got an s7 running Nougat via "The Galaxy Project" rom, the SuperKernel, and i'd really like this feature. The processor is an exynos8890.
I'd love to have this feature, miss it from my old g2.
Click to expand...
Click to collapse
Ask a kernel developer for your device to do that and maybe link him this thread.
Or, if you are one yourself, check the instructions on the linked GitHub page. It's really not difficult at all if you've had since experience with kernels.

doubletap2wake
Where can I get the doubletap2wake v1.0 code that seems like a prereq?

tech927 said:
Where can I get the doubletap2wake v1.0 code that seems like a prereq?
Click to expand...
Click to collapse
I guess you can find it in almost every custom kernel on GitHub, according to your chipset of course.
The most important part is configuring the touch panel to be active and receive input even with screen off. That, however, should be no difficulty for an experienced kernel maintainer

Sent from my Samsung Galaxy J1 Ace using XDA Labs

Hi......may I know if this works with Sony XA1 Ultra? It uses Helio P20.......

eddie24902005 said:
Hi......may I know if this works with Sony XA1 Ultra? It uses Helio P20.......
Click to expand...
Click to collapse
If you already have a custom kernel with dt2w working then this upgrade will work too

tanish2k09 said:
I guess you can find it in almost every custom kernel on GitHub, according to your chipset of course.
The most important part is configuring the touch panel to be active and receive input even with screen off. That, however, should be no difficulty for an experienced kernel maintainer
Click to expand...
Click to collapse
OK I'm new to android kernel development and I'm having my mind melt trying to add the v1 code.
Could you please write a tutorial or make a complete d2w api without needing to hunt for codes. Thanks.

xDoge said:
OK I'm new to android kernel development and I'm having my mind melt trying to add the v1 code.
Could you please write a tutorial or make a complete d2w api without needing to hunt for codes. Thanks.
Click to expand...
Click to collapse
I could and I would if I had time. Just rolled into the fall sem so I'll be a LOT busy. Sorry

tanish2k09 said:
I could and I would if I had time. Just rolled into the fall sem so I'll be a LOT busy. Sorry
Click to expand...
Click to collapse
Why don't you rollback with sem reset hard.

Sorry for double post. XDA app messed the post.

xDoge said:
Why don't you rollback with sem reset hard.
Click to expand...
Click to collapse
Gesendet von meinem SM-G950F mit Tapatalk

may I ask. My device already have featur dt2w/dt2s and sweep up to wake on settings (in Zenmotion). But, unfortunately when I use custom rom this feature gone. Can I use this file to bringing back that feature (dt2w/dt2s)? or maybe adding SU2W too? please help. My device is X00RD