[Guide]Remove Navigation Bar using Adb Commands[No Root] - Nexus 6P General

Hi Guys,
A lot of us are getting new devices that are not yet supported by developers or will never be supported and rooting new devices now a days is getting harder, that's why methods requiring no root are essential.
I was pointed to by @EMJI79 to the original thread of this method by @luisshnyder. Great thanks to both of them. :good:
Requirements:
* ADB and Fastboot installed on PC or Mac.
Instructions:
Type without quotations in CMD or Windows PoweShell(use ".\"before command in PowerShell):
"adb shell wm overscan 0,0,0,-202"
Notes:
1. Make sure to use an alternative navigation app before doing this.
2. To change the height change the values between (0 to -210)see what suits your screen best(for me it was -202).
3. The effect sticks after reboot.
4. To return to normal type without quotations: "adb shell wm overscan 0,0,0,0"
5. This works on all Android versions Oreo and before, it also works on many devices.
6. There are minor bugs stated by the original thread so check them out if you have any, i haven't encountered any yet except you wouldn't be able to see the camera & voice shortcuts in the lock screen.
Finally it's best to combine this with hiding the status bar too, so type afterwards without quotations:
"adb shell settings put global policy_control immersive.status=*"
-If you want to customize on per app basis follow my other guide.
Good Luck!

I can confirm that using the old method of disabling the navigation bar(qemu.hw.mainkeys=1) from the build.prop is working fine with the April security update, also Google now on tap works fine without getting the force close error message.
This guide is rendered useless for users that can access the build.prop. ?

Thank you so much for sharing this, I've been searching for a way to completely hide the navbar without Root. Now Gesture Control can actually be used as intended. ?

My gesture non root setup I wish Google will implement.

Rashad83 said:
I can confirm that using the old method of disabling the navigation bar(qemu.hw.mainkeys=1) from the build.prop is working fine with the April security update, also Google now on tap works fine without getting the force close error message.
This guide is rendered useless for users that can access the build.prop. ?
Click to expand...
Click to collapse
is there any command that enables the navbar on navbar disabled devices?

zohaibahd said:
is there any command that enables the navbar on navbar disabled devices?
Click to expand...
Click to collapse
Use this app https://play.google.com/store/apps/details?id=tw.com.daxia.virtualsoftkeys

For Redmi S2
adb shell wm overscan 0,0,0,-82

ishtiaqe22 said:
For Redmi S2
adb shell wm overscan 0,0,0,-82
Click to expand...
Click to collapse
Im also on redmi s2 running lineage os and 0,0,0,-97 works better for me

is there a way to do the same thing as : "adb shell wm overscan 0,0,0,-202" but for the status bar.
this worked great for my nav bar- but i dont wnt to completely remove the status bar, just move it up a little.
thanks for the respond.

Dear @Rashad83 and other Contributors!
Thank your for this little summary thread, I hope I am not necrobumping right now. I just wanted you to know, that this method is still working flawlessly. My settings for the Umidigi S5 Pro (Android 10): ,,wm overscan 0,0,0,-48"

have anyone tried this on umidigi bison?

infelizmente esse comando não funciona no galaxy s20 android 13
no meu s8 android 10
funciona bem

Related

Easiest way to escape from Oppo R9S malware firmware?

Got an Oppo R9s through aliexpress. First time it arrived the home button wouldn't work, neither the fingerprint scanning. After sending it back and waiting three months I got a working device, but seems to have malware on it.
The lock screen is filled with chinese pictures. Doesn't seem malicious, but I can't remove it. After resetting the device to factory settings it's the first thing that installs itself after giving it network access. The wallpaper option in settings doesn't work. More importantly, when I add a phone contact, the phone app crashes opening as well as the contacts app, which renders the phone completely useless, not being able to make a simple phone call. Also, simple mode doesn't work either.
So my guess this is a modified rom to have some malware always present and basic functionality is either removed or crippled. Following instructions to enter fastboot mode (volume up + power on) seem to enter an endless loop, so it looks like this option is disabled. Using volume down I'm able to enter a recovery mode, where it says it's version 1.2 (root), and allows me to select some rom for flashing.
Before trying to wade through all the threads regarding rooting and flashing, I was considering simply replacing the ColorOS rom with a clean one. However I'm unable to find any for R9s, is it that this model doesn't have one available? Even looking at the international Oppo forums they don't have any R9s download links. So I guess I have to spend some hours reading and fishing links from long threads like https://forum.xda-developers.com/android/help/oppo-r9s-rooting-t3496781 ?
The about info of the device says this is an Oppo R9s, ColorOS v3.0, Android 6.0.1, MSM8953 OctaCore, 4GB ram, build number R9s_91_A.28_191025, baseband version Q_V1_P14,Q_V1_P14, Kernel 3.18.24-G201710252140.
romfury88 said:
Got an Oppo R9s through aliexpress. First time it arrived the home button wouldn't work, neither the fingerprint scanning. After sending it back and waiting three months I got a working device, but seems to have malware on it.
The lock screen is filled with chinese pictures. Doesn't seem malicious, but I can't remove it. After resetting the device to factory settings it's the first thing that installs itself after giving it network access. The wallpaper option in settings doesn't work. More importantly, when I add a phone contact, the phone app crashes opening as well as the contacts app, which renders the phone completely useless, not being able to make a simple phone call. Also, simple mode doesn't work either.
So my guess this is a modified rom to have some malware always present and basic functionality is either removed or crippled. Following instructions to enter fastboot mode (volume up + power on) seem to enter an endless loop, so it looks like this option is disabled. Using volume down I'm able to enter a recovery mode, where it says it's version 1.2 (root), and allows me to select some rom for flashing.
Before trying to wade through all the threads regarding rooting and flashing, I was considering simply replacing the ColorOS rom with a clean one. However I'm unable to find any for R9s, is it that this model doesn't have one available? Even looking at the international Oppo forums they don't have any R9s download links. So I guess I have to spend some hours reading and fishing links from long threads like https://forum.xda-developers.com/android/help/oppo-r9s-rooting-t3496781 ?
The about info of the device says this is an Oppo R9s, ColorOS v3.0, Android 6.0.1, MSM8953 OctaCore, 4GB ram, build number R9s_91_A.28_191025, baseband version Q_V1_P14,Q_V1_P14, Kernel 3.18.24-G201710252140.
Click to expand...
Click to collapse
Are you trying to replace the ROM or just remove the Malware? I've never heard of this device before so I can't point you towards any ROMs, But I can certainly help you remove Malware embedded in the ROM.
theashleyd123 said:
Are you trying to replace the ROM or just remove the Malware? I've never heard of this device before so I can't point you towards any ROMs, But I can certainly help you remove Malware embedded in the ROM.
Click to expand...
Click to collapse
I'm not interested in changing ROMs, just remove the malware that prevents normal device usage. That's why I was asking for links to ColorOS firmware, I presume reinstalling those would restore normal operation. However if that's not possible I'll take any non-malware ROM.
I followed the recommendation from http://community.oppo.com/en/forum.php?mod=viewthread&tid=50113 to use "adb shell" commands and disable ROM programs, finally getting to remove the lock screen pictures. After a while of having the phone turned on, I heard a weird ping sound and then the touch screen stopped responding. It works fine, since I can power off swiping to the right on the off screen, or I can swipe down and play with the toggles, but the launcher and settings app don't seem to receive touches. So maybe I disabled something affecting the screen? I did run:
adb shell pm hide com.android.browser
adb shell pm hide com.android.contacts
adb shell pm hide com.oppo.usercenter
adb shell pm hide com.nearme.gamecenter
adb shell pm hide com.nearme.atlas
adb shell pm hide com.nearme.statistics.rom
adb shell pm hide com.oppo.launcher
adb shell pm hide com.oppo.market
adb shell pm hide com.oppo.music
adb shell pm hide com.sohu.imputmethod.sogouoem
adb shell pm hide com.redteamobile.roaming
adb shell pm hide com.redteamobile.virtual.softsim
adb shell pm hide com.coloros.lives
adb shell pm hide com.nearme.themespace
adb shell pm hide com.nearme.themespacelib
adb shell pm hide com.coloros.pictorial
Rebooting or recovery mode doesn't work, so I figured to install a ROM from https://forum.xda-developers.com/showpost.php?p=70366156&postcount=13 in recovery mode (where the touch screen works fine). After installation the "optimizing android apps" kept there forever, so I turned it off/on manually, and now I launch into the original launcher with a few chinese icons, but still the screen doesn't seem to work.
Touches work for the notifications and such, but nothing for the launcher or settings, so now I'm unable to turn on USB debugging to send adb shell commands. :crying:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
Also try reenabling the input method.
theashleyd123 said:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
I did these after installing replacements, like that post explained. Chrome as browser, Google APKs for contacts/calendar, Novo launcher instead of stock… and everything seemed to be working fine.
I can't enable debugging on the device, adb commands don't seem to reach the device. I've never used sideload before, does it work even without debug mode enabled?
Click to expand...
Click to collapse
romfury88 said:
theashleyd123 said:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
I did these after installing replacements, like that post explained. Chrome as browser, Google APKs for contacts/calendar, Novo launcher instead of stock… and everything seemed to be working fine.
I can't enable debugging on the device, adb commands don't seem to reach the device. I've never used sideload before, does it work even without debug mode enabled?
Click to expand...
Click to collapse
You can sideload an app via recovery by pushing it to /system/app
And then use adb shell chmod 644 "/system/app/APKNAME"
Click to expand...
Click to collapse
theashleyd123 said:
romfury88 said:
You can sideload an app via recovery by pushing it to /system/app
And then use adb shell chmod 644 "/system/app/APKNAME"
Click to expand...
Click to collapse
I can't due to adb not being able to connect to the device, since I can't put it in debug mode. When the device is in recovery mode I can't access it either, I only get "- waiting for device -"
Click to expand...
Click to collapse
Finally managed to flash a good original ROM on the device. Conveniently the chinese rom prevents running dangerous adb commands, but at least I seem to have gotten rid of the malware and I'm able to change desktop wallpapers and the lockscreen magazine
$ adb shell pm hide com.oppo.music
Error: java.lang.SecurityException: Neither user 2000 nor current process has android.permission.MANAGE_USERS.
Click to expand...
Click to collapse
romfury88 said:
Finally managed to flash a good original ROM on the device. Conveniently the chinese rom prevents running dangerous adb commands, but at least I seem to have gotten rid of the malware and I'm able to change desktop wallpapers and the lockscreen magazine
Click to expand...
Click to collapse
hi romfury88 how did u manage to flash original ROM can u guide me pls. thanks
Oppo R9S
ulyong23 said:
hi romfury88 how did u manage to flash original ROM can u guide me pls. thanks
Click to expand...
Click to collapse
Just bought an OPPO R9S and was wondering you managed to flash the original ROM? I have the exact same issues that romfury had.

Fluid Navigation Gestures

Fluid Navigation Gesture​
Installation ​
The app has a built-in option to hide the software navigation keys (if necessary) but it requires either root or a pc is required to grant a system permission.
Instructions:
1-Enable Developer Mode in the Android settings.
2- Enable USB Debugging
3- Install Adb (links bellow)
4- Run the following adb command to grant the
Permission:
Windows: adb shell pm grant com.fb.fluid android.permission.WRITE_SECURE SETTINGS
macOS: Jadb shell pm grant com.fb.fluid android.permission.WRITE_SECURE_SETTINGS
You can restore the navigation keys using the app or by run this
adb command:
Windows: adb shell wm overscan O,0,0,0
macOS: /adb shell wm overscan 0,0,0,0
Actions:
Back
Home
Recent apps
Toggle split screen
Open notifications
Open power dialog
Open quick settings
Launch Google search overlay
Open keyboard selector
Voice Search
Launch assistant
Launch app
Launch shortcut
Download:
https://play.google.com/store/apps/details?id=com.fb.fluid
Hey guys
So I am a beta tester and I made a review of the app with detailed instructions in my channel so for anyone interested to see and understand it
youtu.be/y1X3wQnEMBc
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
stevenlientje said:
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
Click to expand...
Click to collapse
The correct one is android.permission.WRITE_SECURE_SETTINGS
Regurding the fluid app
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
wasp45 said:
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
Click to expand...
Click to collapse
Read the guide. It tell how you can do it.
Have you tried to reboot device after removing it?
Force kill app not work! Pro version
What happens? @@Deadpool96
Sent from my [device_name] using XDA-Developers Legacy app
Unable to restore navigation keys on Yureka Black
I am using Yureka Black device and tried enabling fluid navigation. That worked well. But now i just want to restore my navigation keys but unable to do so. I tried from the app and from the ADB as well (adb shell wm overscan 0,0,0,0) but nothing works. Please help. I have tried rebooting and all
Twrp
Any devs can make a flashble zip for granting cammand through twrp? I iz noob.
does not work on Android 10, quits immediately (Google Pixel 3)
Recent apps
Hi, a little help here.
i have a oneplus 7 (not pro), and i installed FNG in august, and i absolutely loved it
but, since this week's update (i think on sep 21), the gesture for "previous app" changed its behavior. instead of showing the 3 previous app (one swipe changed to the latest, a second one to the one before, a third the one before, and then returning to show the previous app). it was super useful because i drive a cab and could change between 4 apps with ease while driving without little distraction, and also because recent apps has to rotate because it does not support landscape mode anymore (DON'T GET ME STARTED ON THAT, but any help on that would be also very useful).
now, it only shows the last app, and when on android auto it's common that it shows that, which only block the screen and is completely useless.
so, i'm willing to send a lot of good vibrations to whoever can help me with that (that's a once in a lifetime offer, guys). thanks for any help you can offer with this
I have an error running this command : error: device '(null)' not found
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
MikePlays_ said:
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
Click to expand...
Click to collapse
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
MikePlays_ said:
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
Click to expand...
Click to collapse
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
MikePlays_ said:
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
Click to expand...
Click to collapse
That's great news. Hope you get FNG working, with a disabled stock Nav Bar.
It's a terrific app, and one I couldn't imagine without, on my phone and tablet.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
Click to expand...
Click to collapse
Problem I have with it is even smaller pop up over that, it writes when I want to press "ok", it writes "an app is obscuring a permission request. Settings can't verify your response." It is visible on screenshot too, but it has low quality.

I've rooted Fire OS 6.2.7.3 on Firestick 4K

Hi folks, I had a Firestick 4k Fire OS 6.2.7.1 with Wolf Launcher and all was bliss. The OS got updated to 6.2.7.3 and that broke the Home button. I tried all I could find from scouring the XDA forums but nothing worked for me (accessibility apps, adb commands...) The Home key, as well as reboot, always return to the Amazon stock UI. I really miss the Home button returning to the Wolf launcher, as well as long-press of the Home button to get to Network settings because I often switch between my VPN router and normal router. Anyway, I got totally pissed at all the failed attempts and took a chance on rooting the Firestick 4K with Fire OS 6.2.7.3 to see what I could do. I hadn't seen anyone else mention that it could be done on 6.2.7.3, but I can indeed confirm that I was able to do it without issue following the very good 3 part video beginning with this->one (thank you Paul Jones), which begins by showing you how to dismantle the FS4K in order to short it and proceed with the unlocking of the device. It really was not that difficult. Now I have a rooted device with TWRP and Magisk installed and with many possibilities for customization.
I did delete the Amazon home screen (optional in video #3) and when I hit the Home button, it simply went to a blank screen. As I now have root access, with ES File Explorer I was then able to edit the keylayout file for the Amazon remote (/system/usr/keylayout/Vendor_0171_Product_0413.kl) to remap the HOME key to act as a BACK key and that solved that problem, but caused another. If the device went to sleep, I had to reboot the stick because the stock long-press Home button to get to Apps no longer worked. The fix to that was simply to disable sleep mode with ADB (settings put secure sleep_timeout 0). So now, I'm basically to where I was with 6.2.7.1 and the Wolf launcher booting up with the help of FTVLaunchX but now with root access. There's no more Amazon home screen or Amazon app store to get to, however I can still install Amazon apps via the Amazon website to my device. I can also install from a myriad of other sources like Aptoide TV, Downloader...
I still miss being able to long-press the Home button with the Wolf launcher in order to get to Network settings. I've tried all kinds of key mapping apps but none seem to work on Firestick 4K with OS 6.2.7.3. Does anyone know of a key mapping program that actually works with Firestick 4K OS 6.2.7.3? I run Button Mapper no problem on another Android TV OS device but Button Mapper installed on the FS4K does not recognize any key input from the FS4k remote. Its accessibility settings are setup properly but still no joy. Does anyone have Button Mapper working on a FS4k? If so, was there anything special required to get it working? Or, does anyone know where to map events based on key presses defined in the keylayout file?
Alternatively, does anyone know how to create a shortcut on the Wolf Launcher desktop that will allow me to map to the Network settings page? I think you can create shortcuts via ES File Explorer, but I don't know where the Network settings executable is. I know I can just get there with a few clicks via the new Fire TV settings icon, but that's no fun. It would be so much cooler to be able to create shortcuts to specific settings pages or whatever...
I also thought about some kind of wifi widget but the Wolf launcher doesn't allow widgets. ATV Launcher 1.5 does allow widgets but not sure if that works on FS4K.
Sorry for the long post but I'm eager to learn and would appreciate any help or suggestions.
You can try my root Settings replacement.
NewSettingsRoot.apk
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Boot twrp.
adb shell mount -o rw /system
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell "mkdir /system/priv-app/NewSettingsRoot/"
adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/"
adb shell "chown root:root /system/priv-app/NewSettingsRoot/"
adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell reboot
Vendor_0171_Product_0413.kl from 6.2.7.1 attached.
0815hoffi said:
You can try my root Settings replacement.
NewSettingsRoot.apk
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Boot twrp.
adb shell mount -o rw /system
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell "mkdir /system/priv-app/NewSettingsRoot/"
adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/"
adb shell "chown root:root /system/priv-app/NewSettingsRoot/"
adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell reboot
Vendor_0171_Product_0413.kl from 6.2.7.1 attached.
Click to expand...
Click to collapse
Hi 0815hoffi, I have already done that as part of removing the Amazon Home screen. What I am trying to get at is how to achieve long-press Home to get directly to wifi settings, like the Wolf launcher did before it was broken. You can't put in key values in the .kl file to do events. It only contains a value for each key on the remote. Events are coded somewhere else, do you know where that is? Unfortunately, I can't get any button mappers to work on firestick. The other alternative is to find a way to create shortcuts on the main Wolf desktop to get right to the Network settings screen. Is there a way to do that?
In the new settings, where it says to factory reset, do you know if that keeps root and simply wipes the OS clean or does it really factory reset and remove root? Also, what about checking for updates, will that remove root as well? Just curious...
Thanks
NewSettings only launcher the Parts of the original Amazon Settings.
Only Magisk can be Lost, but TWRP is still there.
So if it lost, reflash magisk.zip
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
#!/bin/sh
su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
https://www.google.com/url?sa=t&sou...BMAB6BAgNEAI&usg=AOvVaw1uM2ngLobEuN8uCqybAqNt
Can create shortcuts.
Needs busybox
https://forum.xda-developers.com/attachment.php?attachmentid=5023241&d=1590005330
Thanks, I will give that a try when I get a chance.
0815hoffi said:
NewSettings only launcher the Parts of the original Amazon Settings.
Only Magisk can be Lost, but TWRP is still there.
So if it lost, reflash magisk.zip
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
#!/bin/sh
su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
https://www.google.com/url?sa=t&sou...BMAB6BAgNEAI&usg=AOvVaw1uM2ngLobEuN8uCqybAqNt
Can create shortcuts.
Needs busybox
https://forum.xda-developers.com/attachment.php?attachmentid=5023241&d=1590005330
Click to expand...
Click to collapse
Hi 0815hoffi, the "su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity" command works perfectly in remote adb and opens up the Network settings screen just like I want, but I can't get any shortcut on Wolf desktop to work. I don't know much about programming apk but I tried the "hello world" beginner apk tutorial and was able to save that to my FS4K Wolf desktop. All I really want is the "hello world" apk, but instead of opening a screen with "hello world", on click I would like it to run your script and open the Network settings screen. I don't have enough expertise to be able to program that one line command into an apk. Any help would be appreciated. Thanks again for all your help.
seems like a mess I think i'll stay on 6.2.7.1 as i run magisk and xposed without any issues.
kick60 said:
Hi 0815hoffi, the "su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity" command works perfectly in remote adb and opens up the Network settings screen just like I want, but I can't get any shortcut on Wolf desktop to work. I don't know much about programming apk but I tried the "hello world" beginner apk tutorial and was able to save that to my FS4K Wolf desktop. All I really want is the "hello world" apk, but instead of opening a screen with "hello world", on click I would like it to run your script and open the Network settings screen. I don't have enough expertise to be able to program that one line command into an apk. Any help would be appreciated. Thanks again for all your help.
Click to expand...
Click to collapse
Here a Link to a older Version off my Settings.apk and also the SourceCode as Zip.
This Settings.apk makes many Shortcuts on your Launcher.
Shortcuts you dont need must be hidden in Launcher.
https://forum.xda-developers.com/showpost.php?p=82289861&postcount=1
Maybe that is what you want.
0815hoffi said:
Here a Link to a older Version off my Settings.apk and also the SourceCode as Zip.
This Settings.apk makes many Shortcuts on your Launcher.
Shortcuts you dont need must be hidden in Launcher.
https://forum.xda-developers.com/showpost.php?p=82289861&postcount=1
Maybe that is what you want.
Click to expand...
Click to collapse
Hi again 0815hoffi, I installed the settings.apk and even though I get all the icons on the desktop, they all open the same FireTV Settings page with all options e.g. Sleep, Display & Sound, Network... and the focus is always on the Sleep option. I do want all the icons, but I actually want them to open the correct settings page. For example, when I click on the Wifi icon, I want it to open the Network tab of the FireTV Settings automatically (like running su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity) and not see the FireTV Settings page at all. Mayby this has something to do with having previously installed the most recent NewSettingsRoot.apk that just has the one icon and just opens the FireTV Settings page. I manually deleted the NewSettingsRoot directory from /system/priv-data and uninstalled the settings.apk, re-booted and re-installed the settings.apk and still all icons open the same FireTV Settings page.
Is there something else I need to do. I'm so close to what I want to accomplish. Thanks again.
You must allow root access.
Try to delete Wolf Launcher Data and Cache .
0815hoffi said:
You must allow root access.
Try to delete Wolf Launcher Data and Cache .
Click to expand...
Click to collapse
Still no luck and have allowed root access and cleared Wolf Launcher Data and Cache. Each settings icon still boots the same FireTV settings page.
Not sure what to try next. I will try to find a way of putting my network.sh script file on the Wolf desktop somehow and try to find a way to launch it.
Thanks for your help.
SH Script Runner
Can create shortcuts for sh Scripts.
0815hoffi said:
SH Script Runner
Can create shortcuts for sh Scripts.
Click to expand...
Click to collapse
Yes you had mentioned that in an earlier post and I downloaded it but couldn't get it to work properly. I will try it again. If I still have issues, I will let you know. Thanks
kick60 said:
Yes you had mentioned that in an earlier post and I downloaded it but couldn't get it to work properly. I will try it again. If I still have issues, I will let you know. Thanks
Click to expand...
Click to collapse
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
0815hoffi said:
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
Click to expand...
Click to collapse
Sure, that would be fantastic. Thanks
0815hoffi said:
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
Click to expand...
Click to collapse
Hi again 0815hoffi, hope you are enjoying your holiday. You no longer need to customize that app for me. The curious in me couldn't wait and so I downloaded Android Studio to see what I could do and I finally have a working app that makes a shortcut on my screen that launches the shell command to bring up Network settings. I don't know much about Android apk coding (although I do have programming experience) and likely broke a few Android programming "rules" but I did manage to make it do exactly what I wanted, and that is to have an icon on my desktop that directly launches Network settings. This app also could easily be modified to create a shortcut on the desktop and run any shell command.
I've successfully run this apk on my rooted Firestick 4K with the Wolf launcher desktop and it is only designed to run the Amazon Firestick 4K specific com.amazon.device.settings.action command that you sent me. After installation, you will have to grant root access.
I've attached the apk and zipped source code. Feel free to provide any feedback and thanks for all your help.
kick60 said:
Hi again 0815hoffi, hope you are enjoying your holiday. You no longer need to customize that app for me. The curious in me couldn't wait and so I downloaded Android Studio to see what I could do and I finally have a working app that makes a shortcut on my screen that launches the shell command to bring up Network settings. I don't know much about Android apk coding (although I do have programming experience) and likely broke a few Android programming "rules" but I did manage to make it do exactly what I wanted, and that is to have an icon on my desktop that directly launches Network settings. This app also could easily be modified to create a shortcut on the desktop and run any shell command.
I've successfully run this apk on my rooted Firestick 4K with the Wolf launcher desktop and it is only designed to run the Amazon Firestick 4K specific com.amazon.device.settings.action command that you sent me. After installation, you will have to grant root access.
I've attached the apk and zipped source code. Feel free to provide any feedback and thanks for all your help.
Click to expand...
Click to collapse
?
My code is not perfect either.
It has to work, nothing else matters.
?
kick60 said:
Hi folks, I had a Firestick 4k Fire OS 6.2.7.1 with Wolf Launcher and all was bliss. The OS got updated to 6.2.7.3 and that broke the Home button. I tried all I could find from scouring the XDA forums but nothing worked for me (accessibility apps, adb commands...) The Home key, as well as reboot, always return to the Amazon stock UI. I really miss the Home button returning to the Wolf launcher, as well as long-press of the Home button to get to Network settings because I often switch between my VPN router and normal router. Anyway, I got totally pissed at all the failed attempts and took a chance on rooting the Firestick 4K with Fire OS 6.2.7.3 to see what I could do. I hadn't seen anyone else mention that it could be done on 6.2.7.3, but I can indeed confirm that I was able to do it without issue following the very good 3 part video beginning with this->one (thank you Paul Jones), which begins by showing you how to dismantle the FS4K in order to short it and proceed with the unlocking of the device. It really was not that difficult. Now I have a rooted device with TWRP and Magisk installed and with many possibilities for customization.
I did delete the Amazon home screen (optional in video #3) and when I hit the Home button, it simply went to a blank screen. As I now have root access, with ES File Explorer I was then able to edit the keylayout file for the Amazon remote (/system/usr/keylayout/Vendor_0171_Product_0413.kl) to remap the HOME key to act as a BACK key and that solved that problem, but caused another. If the device went to sleep, I had to reboot the stick because the stock long-press Home button to get to Apps no longer worked. The fix to that was simply to disable sleep mode with ADB (settings put secure sleep_timeout 0). So now, I'm basically to where I was with 6.2.7.1 and the Wolf launcher booting up with the help of FTVLaunchX but now with root access. There's no more Amazon home screen or Amazon app store to get to, however I can still install Amazon apps via the Amazon website to my device. I can also install from a myriad of other sources like Aptoide TV, Downloader...
I still miss being able to long-press the Home button with the Wolf launcher in order to get to Network settings. I've tried all kinds of key mapping apps but none seem to work on Firestick 4K with OS 6.2.7.3. Does anyone know of a key mapping program that actually works with Firestick 4K OS 6.2.7.3? I run Button Mapper no problem on another Android TV OS device but Button Mapper installed on the FS4K does not recognize any key input from the FS4k remote. Its accessibility settings are setup properly but still no joy. Does anyone have Button Mapper working on a FS4k? If so, was there anything special required to get it working? Or, does anyone know where to map events based on key presses defined in the keylayout file?
Alternatively, does anyone know how to create a shortcut on the Wolf Launcher desktop that will allow me to map to the Network settings page? I think you can create shortcuts via ES File Explorer, but I don't know where the Network settings executable is. I know I can just get there with a few clicks via the new Fire TV settings icon, but that's no fun. It would be so much cooler to be able to create shortcuts to specific settings pages or whatever...
I also thought about some kind of wifi widget but the Wolf launcher doesn't allow widgets. ATV Launcher 1.5 does allow widgets but not sure if that works on FS4K.
Sorry for the long post but I'm eager to learn and would appreciate any help or suggestions.
Click to expand...
Click to collapse
I have successfully followed your lead and rooted my 4K 6.2.7.3! I have root, magisk and twrp working.
How do i replace the launcher and make Wolf Launcher default?!
yurividal said:
I have successfully followed your lead and rooted my 4K 6.2.7.3! I have root, magisk and twrp working.
How do i replace the launcher and make Wolf Launcher default?!
Click to expand...
Click to collapse
It's all in the "Unlock and Root a Firestick 4K - Part 3" by Paul Jones. I connect using the iso like the Part 2 video as that worked flawlessly. At about the 45 second mark of the video, it tells you where to download the files and how to go about it.
If one's primary focus is getting a custom launcher working with the Home button (e.g. with FTVLaunchX), would I be able to flash rbox's pre-rooted 6.2.7.1 image via TWRP on top of stock 6.2.7.3 after unlocking with kamakiri?
I'm asking because I'm one of the unlucky people who forgot to block updates and had my unrooted stick update to 6.2.7.3.

How To Guide Activate Native Call Recording Feature for ONEPLUS 9R (without Root)

Oneplus has started to put Google Dialer along with its new android updates. Although, Google Dialer has many functionalities but, it misses out the native call recording of Oneplus Dialer (without the annoying announcement of calls being recorded of the GOOGLE DIALER).
I tried searching all over the internet but could not get Here is the process of activating native call recording in Oneplus 9R.
Install native Oneplus dailer (you can download from the below link)
https://drive.google.com/file/d/1T4UhfxsmFytd8MTBYN7vZZeVWe8yFAvJ/view
(from https://forum.xda-developers.com/t/...th-call-recording-in-oneplus-8t-nord.4189165/)
Activate USB Debugging on your phone from the developer options.
Go to SETTINGS
ABOUT PHONE
tap few times on BUILD NUMBER before activating DEVELOPER OPTIONS
go back to SETTINGS
go to SYSTEM
DEVELOPER OPTIONS
and activate USB DEBUGGING
Install joneplus tools from Playstore
https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en&gl=US
Download Platform tools for android in WINDOWS
USE ADB instruction method from the PLATFORM TOOLS FOLDER
Check if you can find your phone or not
./adb devices
it should show the phone as listed.
after finding your phone as listed, type the following instruction
./adb shell settings put global op_voice_recording_supported_by_mcc 1
This will activate the native call recording feature of ONEPLUS DIALER.
However, the call recorder will be deactivated once you change the sim card or restart your phone. So, you need to install JONEPLUS TOOLS app from GOOGLE PLAYSTORE which will activate the call recording automatically every time you reboot your phone.
You need to provide the permission to joneplus tools by using ADB instruction
./adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
This will allow joneplus tools to automatically restart and activate the call recording every time the phone reboots. Finally, you will have call recording feature in your beloved ONEPLUS 9R.
Is there any method with root other than the axet call recorder & skvalex?
Thanks in advance.
It's weird, I'm getting the recording option right after installing the dialer apk without performing any adb command or installing any joneplus tool. It's staying Even after reboots, I'm on oos 11.2.LE28DA factory firmware, I'm not rooted and bootloader is locked.. it's weird..
Thanks a lot btw.. pretty useful for me..
Hi there,
OnePlus 9R is one of the most recent devices prior to the OnePlus 10 Pro that just received its global release.
Same thing there, comes with Google Dialer stock. The above apps work on that phone too, but jOnePlus Tools does not install, and the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 does not execute.
I made a post similar to yours on that forum, with the difference we are stuck without understanding why.
Could you please help us understand why this command does not work on our phones as compared to the Oneplus 9R?
It would help that community a lot.
Here's a link to my post:
Enable Native Call Recording + OP Stock Dialer on OnePlus 10 Pro
Hi guys, Just upgraded from OP7T to OP10 Pro as a European user. Call recording functionality does not come with the device here. Had native call recording enabled on my OP7T through jOnePlus Tools and the likes. Jtools Oneplus does not install...
forum.xda-developers.com
Thanks a lot in advance
Edit: Found a working solution. All I need now is to understand how to write a Tasker task to automate the adb command upon each reboot. This is what jOnePlus Tools normally took care of, but since we can't install it on that device..

How To Guide Call recording working in GT 2 pro ( no root )

Finally i found a method to record call on realme gt 2 pro global gdpr version, who is persistent at boot. No root, no bootloader unlock.
Step one : install setedit from play store and add op_voice_recording_supported_by_mcc with 1 value to global settings. You have to give Setedit write secure rights with adb
Step two : install phone apk below.
That's it. Start Google dialer and make a call. Still works after reboot.
Not working : automatic call recorder, you have to press record button when you're in call.
Notice: if you don't see record button in Google dialer , is normal, just press back button to see realme dialer.
This should work on all color os 3 device.
Recorded call are in internal memory / music/ recordings/ call recordings folder.
ENJOY !!
No working... No see
Which apk needs to be installed for step two?
NVM I figured it out
Not working, it has changed the dialer but instead of recording button I have a "contacts" button and when I press it nothing happens.
Please uninstall phone from installed apps and install again.
criszz said:
Please uninstall phone from installed apps and install again.
Click to expand...
Click to collapse
Same, tried also to reboot but nothing
No permission to add a new line in Global Table
RazvanelTM said:
No permission to add a new line in Global Table
Click to expand...
Click to collapse
Same here, I've added the option in the system table maybe that's why it is not working
Yes, you must provide write secure rights for setedit with adb to edit in global.
Updated first post with that.
criszz said:
Yes, you must provide write secure rights for setedit with adb to edit in global.
Updated first post with that.
Click to expand...
Click to collapse
How can do? Have any tutorials?
manu81cba said:
How can do? Have any tutorials?
Click to expand...
Click to collapse
By default, for your protection, Android prevents you from modifying the SECURE and GLOBAL tables. If you have Android Jellybean or later, you can remove this protection from an ADB shell using the command "pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS". On earlier versions, you can only remove this protection on a rooted device by installing SetEdit to the system partition.
All working flawless now I can confirm that
Not working when giving the permission in adb
RazvanelTM said:
Not working when giving the permission in adb
Click to expand...
Click to collapse
Try to activate first in the developers options this one: "Disable permission monitoring"
shootemdown371 said:
Try to activate first in the developers options this one: "Disable permission monitoring"
Click to expand...
Click to collapse
It worked, thanks!
Now it's confirmed to work and we must think how to enable automatically record for all calls. People who said not working without knowing, please edit your post.
In setedit ...you know what need change for active the volte ?
Thank you very much it's working for me!
PS for those unfamiliar with SetEdit can also use this in adb after disabling permission monitoring:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Just must be applied after every restart ( that is what i read )
Nice post, thanks for sharing. Any solution for Xiaomi Redmi Note 10S, Global ROM MI?
Also working on the regular gt2

Categories

Resources