Database Users

[Guide] Expanding the limit of multitouch points (root needed)

Let's cut the crap. Seems like somebody on a Chinese forum figured out the way to apply the mod to MM2. I just translate it into English.
1. Download the attachment and unzip milestone2_more.ko to the root of sd
2. mount /system/ r/w
3. copy milestone2_more.ko to /system/lib/modules/
4. open terminal emulator
5. input the following command
su
chmod 644 /system/lib/modules/milestone2_more.ko
insmod /system/lib/modules/milestone2_more.ko touch_num=6
(the guy said if you choose a number greater than 6 the system will crash)
now you should get a 6-point-multitouch
original thread: http://bbs.gfan.com/android-1997547-1-1.html

Thank you soooooooo much! )))

Works but MT is still buggy...

oh my god.. thank you, it works.
5 is more than enough

OMG!! You made my day!
Sent from my A953 using XDA Premium App

Is this permanent? Or it'll go away when we reboot?
Sent from my A953 using XDA App

It will go away when you reboot, but its not a big deal to use the command again
Sent from my A953 using XDA Premium App

Just make a init.d script to load it up when the system boots and you won't have to worry about it again..

Just did this, but I think i wrote it wrong. Please correct me
I created a blank file and wrote inside it:
insmod /system/lib/modules/multitouchfix.ko (I replaced the name)
And saved the file as 99multitouchfix inside /system/etc/init.d/
I also fixed permissions for both files
Sent from my A953

Is it working Aragorn?

Thank you. I'll try it when I get home!

inheme said:
Is it working Aragorn?
Click to expand...
Click to collapse
Nope. The module works, but not the init.d script

you can use autostart from Market

AragornPE said:
Nope. The module works, but not the init.d script
Click to expand...
Click to collapse
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.

dangpzanco said:
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.
Click to expand...
Click to collapse
I'll try that as soon as my M2 wakes up, long day for it today =P

Actually,the patch is developed by korean , the XDA thread is http://forum.xda-developers.com/showthread.php?t=1162327
Autoload after reboot: copy install-recovery.sh to /system/etc and set rwxr-xr-x .
If you wanna change the touch point limit , open install-recovery.sh with text editor , change the number that follows "touch_num=". The range is 1~10.
My own test shows more than 6 touch points will NOT lead to system crash , but make it back to 2 points...orz. Since the same patch on D2/D2G/DEFY enable up to 10 points, why
m2 cound not
Ah, forgot to say , the autoload patch is ported from http://bbs.gfan.com/android-1997547-1-1.html

Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953

Install recovery didn't work either
Maybe I'm doing something wrong?
Sent from my A953

AragornPE said:
Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953
Click to expand...
Click to collapse
Did you set the permission properly，both milestone2_more.ko and install.sh.

All works fine, both the milestone2_more.ko and the install recovery, no problem at all, have 4 MT points now

[GUIDE] [NOUGAT] Viper4Android

//Thank you all for 30k+ Views. You're amazing guys//
You want Android 8 with Viper4android to?
Thread created check my profile...
Hi,
at first im not responsible for anything that happens to your phone OK?
Fine Let's Start.
If you are on cm skip all until the cm section
Supported kernel list and known errors/bugs see second post
Step 1
- Flash full Factory Images.
- Install TWRP, remember you have to be decrypted.
Step 2
- Install Android 7 ROM by tupac4u / or any other rom / or leave stock
- Reboot //if nessesairy
Step 3
- Flash ElementalX's N Kernel.
- Flash Viper5.0_Stock.zip in Recovery / or any other viper
- Reboot.
Step 4
- Install driver.
- Open File Explorer and delete /system/vendor/etc/audio_effects.conf
- Reboot.
Step 5
- Set enforcing to permissive (You have to do it at every Reboot!).
- In Viper open Menu->FX-CompatibleMode->yes // you can try without, it may work
- Enjoy Viper.
CM Section
1. Flash arise sound mod ( link down below )
2. And IMPORTANT flash super su
3. Disable audio fx and reboot
SPOTIFY FIX
1. Download that file
https://drive.google.com/file/d/0BxyY1q0qeeeEeUFGT3JHeDZLZkE/view
2. Place it under /system/etc
3. Reboot
PURE NEXUS ONLY WORKS WITH BUILD 10/25!!!
If it worked leave a reply.
Alternative Download link for ARISE Viper here:
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

Unsupported Rom/Kernel
Kernel:
- Stock
- Jolla
ROM:
F.A.Q.
Q: Spotify isn't working with that
A: Force enable Viper4Android and turn FX Mode to compatible. Then restart both applications.
Q: Why ElementalX Kernel?
A: That's the only Kernel who works with Viper except Stock kernel. Elite Kernel may also work but it hasent been updated since the Dev Previews.
Q: Is that also working with the stock rom?
A: Yup. Also works with (nearly) any stock based ROM.

Is there a definite way of checking if it's working? Not by sound?

Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Sent from my Nexus 5X using Tapatalk

how to set permissive mode permanently?

Nightshadow931 said:
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Click to expand...
Click to collapse
I found that it isn't working on jolla Kernel and Stock.

Did you enable viper in app itself?
Not sure, but maybe you need to enable it on order to see 'processing'..
Did the installation of driver went well?
Sent from my Nexus 5X using Tapatalk

enzippo said:
how to set permissive mode permanently?
Click to expand...
Click to collapse
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.

Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".

Try some other app like play music, v4a won't work on all apps if they have their own equalizer.
Sent from my Nexus 5X using Tapatalk

Blinkiz said:
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Click to expand...
Click to collapse
For those who want to use Viper4android with Spotify change fx compatible Mode to compatible in Viper settings. Then Open Spotify and go to Settings->Equalizer that should bring up Viper. Select Force enable and close Viper and Spotify. Open up both again and Boom Viper is there.

How find Android 7 by tupac4u ??
EDIT.
I found him already

Did someone get it working with stock rooted ROM?

noidea24 said:
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Click to expand...
Click to collapse
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.

trhacker01 said:
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
Click to expand...
Click to collapse
In gonna give it a try

Nightshadow931 said:
Did someone get it working with stock rooted ROM?
Click to expand...
Click to collapse
Me not

Thargorsson said:
In gonna give it a try
Click to expand...
Click to collapse
Nope it don't works

Thargorsson said:
Nope it don't works
Click to expand...
Click to collapse
thats how im running right now, just checked. only with the universal init.d though

noidea24 said:
thats how im running right now, just checked. only with the universal init.d though
Click to expand...
Click to collapse
Ur saying that permissive zip works with the universal init.d?

trhacker01 said:
Ur saying that permissive zip works with the universal init.d?
Click to expand...
Click to collapse
As long as the zip creates/places a file in the init.d to change selinux then i guess it should work

My selinux status got enforcing instead of permissive

I searched lots of things to make it permissive...
I did this things
1)
/etc/init.d directory, create a file and rename it as 08setperm
2)
Added lines on that file
#!/system/sh
setenforce 0
It did work but when i tried rebooting it didn't...
Im using cm14.1 official..
I can't wipe anything because my storage is full
Twrp doesn't give me permission to do that and says selinux not premssive...
How to do it then?? I want it permanently not for temp purpose

Have you tried SELinux Mode Changer app? http://forum.xda-developers.com/showthread.php?t=2524485

acejavelin said:
Have you tried SELinux Mode Changer app? http://forum.xda-developers.com/showthread.php?t=2524485
Click to expand...
Click to collapse
But that's for temp use bro...
I can't add exposed....

Sagar_1401 said:
But that's for temp use bro...
I can't add exposed....
Click to expand...
Click to collapse
Yes you can. Set it where when the phone boots it notifs you that its changed to permissive. I've used it on LP, MM, and now 7.1. I've used it with Xposed and Viper just fine

L-OS Can't turn of double tab to wake

I've installed the newest Lineage OS, but I want to turn of "Double Tab to wake". But after one day, it automatically turned on again, but without showing it in the settings (showed that it's turned of). Now I have the question if there is any possibility to turn it off?
Thanks,
Philipp

The setting does not stick after the reboot. You have to enable it and disable it again. Then it should be really disabled until the next reboot.

Okay, thank you. I hope they will fix it soon

I think it may be because you flashed a custom kernel.
Some custom kernels break dt2w

barni090 said:
I've installed the newest Lineage OS, but I want to turn of "Double Tab to wake". But after one day, it automatically turned on again, but without showing it in the settings (showed that it's turned of). Now I have the question if there is any possibility to turn it off?
Thanks,
Philipp
Click to expand...
Click to collapse
Until they fix this you can use a script to disable it. Use init.d or any automate app to run the script at boot. It'll turn off the tap2wake.
#!/system/bin/sh
tap2wake=/proc/touchpanel/double_tap
echo "0" > $tap2wake

could you maybe tell me how to use this command? Sorry for that, but I am new in that and don't know what to do

barni090 said:
could you maybe tell me how to use this command? Sorry for that, but I am new in that and don't know what to do
Click to expand...
Click to collapse
Since you're new to this I'll give you the easiest way to do this.
1. Download the script from the link given below. (or use my last post's code to make a script yourself)
2. Put it in a folder in sdcard.
3. Install 'init.d scripts support' app from play store.
4. Open the app & tick 'try to aquire root privileges'. Grant root access.
5. Tick 'run scripts at boot time' option.
6. Set 'execution delay' to a desired time.
7. Select the folder you put the downloaded file.
Tap2wake disable script - http://www.mediafire.com/file/r4h5z8p1ez21jpi/tap2wakedis.sh
Done. Now every time you reboot, app will execute the scripts in the selected folder which contains our script to disable double tap2wake.
You can always execute the script using ini.d, su.d, tasker, macrodroid etc.

I have some problems with activating it, I've put the error message as attachment maybe you could look over it.

barni090 said:
I have some problems with activating it, I've put the error message as attachment maybe you could look over it.
Click to expand...
Click to collapse
I forgot to change the line ending to Unix. I edited the post check it again.

It's still not working, I used another app and it's telling me permission denied. But thank you for your help

barni090 said:
It's still not working, I used another app and it's telling me permission denied. But thank you for your help
Click to expand...
Click to collapse
Try the link again this time it should work. lol. I've added /bin/bash not /bin/sh. old habits. If you're using a terminal issue 'su' first then 'sh SCRIPT_PATH'.

worked now Thanks so much :victory:

[GUIDE] Easiest way to root Pixel 2 XL and disable the carrier tether check!

***PIXEL 2XL ONLY!!!*** ***PIXEL 2XL ONLY!!!*** ***PIXEL 2XL ONLY!!!***
Confirmed this works with Android O and P!
UPDATE 3/17/2020: Now confirmed this works with Android Q, but with slight modification!
It took me many hours to piece together the various forums and articles, but these instructions will have you up and running in 30 mins max!
*Below instructions assume brand new phone out of the box, everything stock.
1. Download adb and fastboot on your computer. You don't need the whole SDK and don't need to install anything; Google now provides them in a simple zip file. Get it here for Windows, Linux, Mac. If you're using a Mac, all you have to do is open Terminal, cd into the directory where you unzipped the files, and type ./adb [command] from there. EX: If you downloaded the zip file into your Downloads folder, and extracted the zip also in your Downloads, you'd type the following on a Mac:
Code:
cd ~/downloads/extractedfoldername
Code:
./adb version
with your phone plugged in via USB to the computer to test adb works. Make sure to enable developer mode on your phone, and also enable USB Debugging. NOTE: For all below references to adb and fastboot, make sure to include the "./" before the command from the extracted directory. EX: "./adb" and "./fastboot"
2. Unlock bootloader. Follow the directions provided here in the "Unlock the bootloader of the Pixel 2 / Pixel 2 XL" section. (Don't waste your time reading the rest of those instructions, since that will confuse you and they don't work anyways.) I did unlock_critical at first, but the bootloader still said it was locked. Then I did "flashing unlock" and that unlocked the bootloader. Make sure device status in fastboot on the phone says "unlocked." Reboot the phone.
3. Download the latest Magisk Manager from here to your computer. I used 5.6.4.
4. Type
Code:
./adb push <path_to_file> /sdcard/Download
5. On the phone, go to your Downloads app and install the Magisk Manager apk.
6. Open the manager. Click the Install button. It will ask if you want to "install Magisk-vXX.zip now". Click Install and then select Download Zip Only at the next prompt.
7. Download the TWRP image here to your computer. NOTE: You only need to download the IMG file! Don't need the zip file.
7.5 From your computer, run:
Code:
./adb reboot bootloader
8. From your computer, run:
Code:
./fastboot boot path/to/twrp.img
9. Once phone boots into TWRP, go to Install. Then go to the MagiskManager directory. In there, you should see the "Magisk-vXX.zip" file you downloaded in Step 6.
10. Now reboot your phone and open up the Magisk app. You should now see it says "Latest Version: vXX.X" and "Installed Version: vXX.x" with green check marks next to the items. Open the Magisk settings (3 bars on the top left) and you should see a bunch of options, one of them says #SuperUser. This means you now have root!!
11. To enable the tethering:
For Android 8 and 9:
Code:
./adb shell
Code:
su
**(grant permission if phone asks)**
Code:
mount -o rw,remount /system
Code:
echo "net.tethering.noprovisioning=true" >> /system/build.prop
Very important step! You must reboot for the changes to take effect.
Code:
reboot
For Android 10
It seems like you can no longer mount /system as rw. So it's a little more complicated. If you fully installed Magisk (not the way I did it above), then from Magisk Manager, go to Modules and download MagiskHide Props Config and busybox-ndk. Follow the instructions here to run the Props Config.
If you followed my rooting instructions above, running the Props Config won't work, but there is a workaround.
You could still use the module, but instead of using the props command and the terminal UI, you just use the configuration file to set everything up. Download the settings file, extract it from the module zip (in the /common folder) or copy it from the module directory under /data/adb (in the /common folder), add
Code:
net.tethering.noprovisioning=true
to the CONFPROPS variable, place it in the root of your internal storage (/sdcard) in /data or in /cache (or /data/cache if you're using an A/B device) and reboot.
Another option is to just use a simple boot script. Put the following in a file (doesn't matter what you name it) in /data/adb/service.d:
Code:
#!/system/bin/sh
resetprop net.tethering.noprovisioning true
Give it execution permission (chmod 755 is usually the goto) and then that prop will be set at each boot. If it doesn't seem to work, put the script in /data/adb/post-fs-data.d instead.
Very important step! You must reboot for the changes to take effect.
Code:
reboot
[email protected]##
Giant shoutout and thank you to @Didgeridoohan for helping me debug and figuring this out! You're a life saver.
References:
MagiskHide Props Config Documentation thread
MagiskHide Props Config README
Thread where Didgeridoohan explains the process and help me debug

Codes
Hi im having trouble with getting the commands right, I seem to be getting the message stating the command push requires argument but im not sure why, can you provide the actual command in full how it should be input.
Thanks

I didn't even bother using the commands. All I did was root as given in the guides for this device. I then used a file manager with root capability to access build.prop and edit the file directly to add the line. Afterward I rebooted and was all set.
Of course, with my service provider I may not have needed to do this as their provisioning doesn't seem to touch tethering, even though they don't allow it. I'll find out next month when the security update comes through.

Excellent guide, except for one crucial missing step:
7.5 Reboot back into the bootloader:
Code:
adb reboot bootloader

I'm on a grandfathered att unlimited plan, which does not allow tethering. I have edited the build prop to enable it, but does anyone know if they can detect that I am tethering?

Need help.
i accidentally used this for a pixel 2 and now cannot get past the white startup screen with the google logo. Any ideas?

ashayden said:
I'm on a grandfathered att unlimited plan, which does not allow tethering. I have edited the build prop to enable it, but does anyone know if they can detect that I am tethering?
Click to expand...
Click to collapse
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.

Strephon Alkhalikoi said:
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.
Click to expand...
Click to collapse
This is a true statement.

frankygoes said:
Need help.
i accidentally used this for a pixel 2 and now cannot get past the white startup screen with the google logo. Any ideas?
Click to expand...
Click to collapse
I'm having the same issue. I previously used the build.prop updated a number of times, but after doing it with the July factory images, I get stuck on boot. Anyone figure out a way around this?

I did this method and have root but I have no recovery.
According to this: https://twrp.me/google/googlepixel2xl.html I needed to install twrp zip after fastboot boot twrp.img and I can't do it now because I'm rooted and need to reflash boot image. dang!
/necro

soccercake7 said:
I did this method and have root but I have no recovery.
According to this: https://twrp.me/google/googlepixel2xl.html I needed to install twrp zip after fastboot boot twrp.img and I can't do it now because I'm rooted and need to reflash boot image. dang!
/necro
Click to expand...
Click to collapse
You don't need reflash your boot image. Just put your phone into recovery, then go back to temporary twrp by fastboot boot twrp.img. Then flash twrp.zip

Strephon Alkhalikoi said:
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.
Click to expand...
Click to collapse
Not entirely true if your device is fresh out the box. On my previous phone when we were all trying to unlock the bootloader on the Verizon variant, I did it accidentally. I failed to unlock the bootloader lol, but if you never put a Sim in the device and delete the radio file to temporarily "un-grey" the OEM unlock ticker, and then install a vpn (I used the cracked adguard plus from revdl) and turn on basically everything, then factory reset to get the radio back, then reinstall the vpn and enable all the ad masking options and THEN put your sim in for the first time...
I don't know how or why it works but I went almost three months tethering my heart out on Verizon for like 400-700 gigs/month without being throttled one bit or subjected to their bull**** priority system. An added peculiarity was I also had glasswire data moniter installed before ever inserting the sim and both it and the Verizon built in data meter both just stayed at zero. Unfortunately, I was sending a file to a friend with sendanywhere and we were having trouble getting it to accept the access code so I turned off the adguard protections just for like two minutes and both data monitors started spitting out numbers and I got throttled into Oblivion the following bill cycle.
Again, I don't know how many of those steps are needed or what exactly to turn on in adguard, but I do know that it somehow let's you in the data door and keeps the traffic source anonymous until you give the device a window to phone home with your account. Wish I could be more specific with directions but it absolutely worked, somehow. I haven't used sendanywhere since that day and never will again because it ruined something so beautiful for me.
I tried for probably two dozen hours to reset and recreate the circumstances and get those sweet, sweet zeroes back, but to no avail, so I would assume that it can't ever work on the device once it's had a Sim installed even for a moment, and once working you must keep the vpn running from startup forever...probably can't ever factory reset or you will lose it. I really don't know. I'm sure one of the techier peeps here could figure out how and why it works or already knows, but doesn't want to post it because then it will get fixed and ruin his or her own beautiful thing.

8wrlobo said:
Not entirely true if your device is fresh out the box.
Click to expand...
Click to collapse
https://android.stackexchange.com/q...-companies-detect-tethering-incl-wifi-hotspot
You got lucky.

Strephon Alkhalikoi said:
https://android.stackexchange.com/q...-companies-detect-tethering-incl-wifi-hotspot
You got lucky.
Click to expand...
Click to collapse
I use NordVPN and VPN Tether on rooted (Magisk) stock Google Pixel 2 XL . Carrier doesn't see my tethering.

n2music said:
I use NordVPN and VPN Tether on rooted (Magisk) stock Google Pixel 2 XL . Carrier doesn't see my tethering.
Click to expand...
Click to collapse
A VPN if I recall doesn't prevent the carrier from using the number of hops (i.e. the TTL number) to detect tethering. It does prevent them from seeing what data you are pushing across the network however.

My total data use increases, but tether usage does not. I rarely use more than 30gigs altogether each month anyway, not an abuser.

n2music said:
My total data use increases, but tether usage does not. I rarely use more than 30gigs altogether each month anyway, not an abuser.
Click to expand...
Click to collapse
Not an abuser, but in the eyes of the carriers that don't want you tethering without paying you are a thief. It's silly because in the end it's still data, and just a way for the carriers to gouge you.

Strephon Alkhalikoi said:
Not an abuser, but in the eyes of the carriers that don't want you tethering without paying you are a thief. It's silly because in the end it's still data, and just a way for the carriers to gouge you.
Click to expand...
Click to collapse
I actually do pay for it. I am on beyond unlimited. But I agree with you.

n2music said:
I actually do pay for it. I am on beyond unlimited. But I agree with you.
Click to expand...
Click to collapse
Sorry for assuming you didn't pay for the privilege. Since the discussion started by others centered on ways to prevent carriers from detecting tethering, I ran on that assumption.