Related
There are a couple of people whose navigation bar on their N4 isn't working. I'm talking about this.
Found a github repository which contains the fix (credits to gkraynov) for all stock releases: https://github.com/gkraynov/nexus-4-navfix
I've recently installed this ROM, which has a different build number (LMY48G), so this solution would not work for me, because stock 5.1.1 has LMY47V.
The fix (source): https://android-review.googlesource...droid/systemui/statusbar/policy/DeadZone.java
My steps were:
1.) Decompiled the SystemUI.apk with apktool (to get to the smali file):
Code:
java -jar apktool.jar d SystemUI.apk
Here's the decompiled source in a zip file.
2.) Decompiled the same apk with http://www.decompileandroid.com/ to get the java source
3.) Compared the source of the fix with corresponding smali and java file, like in this image.
4.) Recompiled with:
Code:
java -jar apktool.jar b SystemUI
5.) Pushed the apk back to the phone:
- set root access for adb and apps on phone under developer settings
- adb root
- adb remount
- adb push SystemUI.apk /system/priv-app/SystemUI.apk
After that I rebooted the phone, which didn't display the navbar anymore, so I've must have made a mistake somewhere.
Can someone, please, take a look and tell me, what I did wrong? I have zero experience with this.
You can share files you edit?
You didn't set perms right. Reboot to recovery and fix permissions or just change the permissions to
RW-R--R--
I also want to wear a custom rom , but the nav bar I do not work , if you can help ?
chmod?
Can anyone compile this source with android 6.0 marshmallow
Sent from my Nexus 4 using Tapatalk
I tried, I've tried to edit Deadzon.java but I am confused as to restore the file to dex for compile into apk again
I did the same thing using TMA to decompile and to update and got the same issue.
No more NAVBAR.
Any clue?
It appears that the code edit it`s not correct.
Using another tool http://bytecodeviewer.com/ to reverse engineer it appears wrong.
I am also newbie at this.
Can someone help?
same here
I have encountered the same issue with my N4.
To fix it, I tried a stock reset. Did not work.
Than I granted myself root access, installed CyanogenMod, which then allowed me to use the "pie"-Navigation, which works great.
I also found out, because of the full screen option etc., that the area of the screen of the broken navigation bar should be working, as it appears to work in different apps in landscape-mode.
So... My problem is now that I can't try out the patch you writing about because now I am using CM13, not the Stock Version which the fixes are referring to.
I am really new to all this ROM stuff (all I know about it is from this very day) - So, is there a way of applying this way of fixing the navigation bar to CM13?
Thank you.
Sackhaar said:
I have encountered the same issue with my N4.
To fix it, I tried a stock reset. Did not work.
Than I granted myself root access, installed CyanogenMod, which then allowed me to use the "pie"-Navigation, which works great.
I also found out, because of the full screen option etc., that the area of the screen of the broken navigation bar should be working, as it appears to work in different apps in landscape-mode.
So... My problem is now that I can't try out the patch you writing about because now I am using CM13, not the Stock Version which the fixes are referring to.
I am really new to all this ROM stuff (all I know about it is from this very day) - So, is there a way of applying this way of fixing the navigation bar to CM13?
Thank you.
Click to expand...
Click to collapse
I am facing the same issue.
But I am trying to create the patch for Paranoid Rom. If I suceed I think the same concept can be use for any other rom.
Hi all..
does anyone want to help me to update this patch for Lineage OS??
https://github.com/gkraynov/nexus-4-navfix
I know some international versions of the S7 have the data toggle in their drag down. Obviously AT&T HAS to remove it to inconvenience their customers......
How do we go about putting it back in? Would it be something like it was on the S5? (see here - http://forum.xda-developers.com/showthread.php?t=2721550)
Currently at work, but I'll be taking a look at this once I'm home.
---
edit - looks like I've found something from a German forum!! http://www.android-hilfe.de/thema/r...ixperience-s7-port-stable-v3-1.759967/page-33
I'm testing this now, hopefully my phone reboots
edit 2 - failure. Maybe someone else can see where I went wrong?
*DISCLOSURE - only follow the below if you are comfortable with messing up your phone. I will not be reliable for your damaged phone, if something does go wrong*
Based on the thread I found in German above, you have to edit "sysui_qs_tiles". For some reason, SQLite Editor cannot find that file, but Settings Database Editor(SDE) by 4A does.
Once SDE has been installed, head to secure, and scroll down until you see "sysui_qs_tiles"(see attached screenshot). When you click to edit it, you'll get a permissions error.
To stop the permissions error, plug phone into computer, open where your ADB is installed, then open an Administrator command prompt there. (start-> type "cmd" -> right click and select administrator, then type "cd c:\adb", or where your ADB is stored) You should do "adb devices" and then see your devices. If you do, paste this "adb shell pm grant by4a.setedit android.permission.WRITE_SECURE_SETTINGS". The next time you click on "sysui_qs_tiles", you'll be able to edit it.
The German thread says to reference this:
Wifi,Location,SilentMode,RotationLock,Bluetooth,MobileData,PowerSaving,AirplaneMode,DormantMode,Flashlight,UltraPowerSaving,WifiHotspot,PersonalMode,AllShareCast,Sync,Aod,SFinder,ScreenCapture
Click to expand...
Click to collapse
I tried inserting MobileData, but when I restart, there is no new MobileData tile (the MobileData addition stays in the "sysui_qs_tiles" though).
Any thoughts?
edit 3 - tried it one more time, and I added the screenshot tile!! Looks promising, but we would need to find the name for the mobiledata tile.
Delete
I am on PK1 and after flashing engboot i didnt like the way my phone ran so I flashed AP file of PK1 and now suddenly I have data toggle. I never even rooted with engboot or did any other adjustments to try and get the toggle.
Solved Is there a way to disable "10 attempts remain before device data is deleted"
I'm on a VZW 7.0 stock s-off locked rooted (SuperSU systemless) busybox systemless
Is there a way to stop Android from erasing the phone if the lock screen is
misentered 10 times? I mean other than turning off the lockscreen.
Thanks
fuzzynco said:
I'm on a VZW 7.0 stock s-off locked rooted (SuperSU systemless) busybox systemless
Is there a way to stop Android from erasing the phone if the lock screen is
misentered 10 times? I mean other than turning off the lockscreen.
Thanks
Click to expand...
Click to collapse
You can edit the system\customize\ACC\default.xml
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]10[/B][/COLOR]</item>
[B][COLOR="Red"]to[/COLOR][/B]
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]0[/B][/COLOR]</item>
andybones said:
You can edit the system\customize\ACC\default.xml
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]10[/B][/COLOR]</item>
[B][COLOR="Red"]to[/COLOR][/B]
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]0[/B][/COLOR]</item>
Click to expand...
Click to collapse
That worked, but I lost advanced calling, (presumably due to modifying /system), sigh.
Restored system from TWRP backup and advanced calling works again,
I wonder if there is a way to do it with Magisk?
fuzzynco said:
That worked, but I lost advanced calling, (presumably due to modifying /system), sigh.
Restored system from TWRP backup and advanced calling works again,
I wonder if there is a way to do it with Magisk?
Click to expand...
Click to collapse
Sorry I should had realized that from your OP.
A Magisk module can def be created I'm sure, however I haven't dug into creating any, so I'll take a look - but if others are reading this and don't mind lending a hand that's be great.
andybones said:
Sorry I should had realized that from your OP.
A Magisk module can def be created I'm sure, however I haven't dug into creating any, so I'll take a look - but if others are reading this and don't mind lending a hand that's be great.
Click to expand...
Click to collapse
1. Copy (don't move) default.xml from \system\customize\ACC to a new folder \cache\magisk_mount\system\customize\ACC\.
2. Edit the copied (not original) default.xml in the magisk_mount subfolder as per @andybones' instructions in post 2.
3. You should be good to go.
I have made other tweaks (from time to time) in that file and Magisk mounts it just fine.
.
Works ! with advanced calling.
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:
***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.