Related
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
For the powersaver mode, try this from a computer with working ADB
Code:
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
Code:
hide_ui_user_powersaver=1
Then try
Code:
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Must have missed that one. I went through that post a couple days ago. Guess this will work for those that can't or don't know how to setup and use adb
Sent from my HTC6545LVW using Tapatalk
Evocm7 said:
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
Click to expand...
Click to collapse
If it is like the M9 on marshmallow, after making that edit, if you factory reset it, the menu option should appear in the standard menu. its alot easier to either put it in as a shortcut, or use xtended settings, and add it to the power menu, or gravity box, and add custom quicksetting tiles (1 of which being battery, it will also show battery temp and mAh remaining).
Once we get a deodexed based, or even a stock odex flash, we can make those edits prior to flash and it will be in the menu as normal
edit, i also believe if you edit the next line (120) def_hide_ui_user_powersaver and set it to 0, this is what will enable the menu on factory reset
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
hgoldner said:
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
Click to expand...
Click to collapse
Can confirm that the latest update definitely does break this ability (no root). =(
im_high_tech said:
Can confirm that the latest update definitely does break this ability (no root). =(
Click to expand...
Click to collapse
I think the only way to do this is to write to \system; so for those who don't want to flash a custom ROM or write to \system, it's out of reach for now.
And especially galling because the 10's on all the other carriers have the feature. Verizon kills it.
@andybones has it in the stock deodex base, but if you are working off of the odex base, the easiest way is probably gravitybox, and using the QS tile to toggle it (still requires root). Just make sure you are using systemless xposed to not touch the system partition as @hgoldner pointed out, if you need it.
by stock base, i mean OTA to 1.19.605.22
Battery Saver Mode Settings
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
klarthur said:
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Click to expand...
Click to collapse
This modification can be done using Magisk, without editing /system. You need to cache-mount the edited default.xml using Magisk, and Magisk mount the patched SystemUI.apk and HtcPowerManager.apk from @andybones' deodexed stock ROM. HUUUGE thanks to @Captain_Throwback for helping me figure this out and tolerating all-too-frequent stupid mistakes getting to this point, and, of course, none of this would be possible without the amazing efforts of @topjohnwu in creating Magisk in the first place.
I will post detailed instructions if someone is interested.
jackebuehner said:
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
Click to expand...
Click to collapse
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Chewieez said:
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
jackebuehner said:
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
Click to expand...
Click to collapse
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
mrbacks said:
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
Click to expand...
Click to collapse
You'll likely need a custom kernel for that, which means root access and either unlocked bootloader or S-OFF. Once you're in that boat, you'll need Magisk to clear Safety.net. It's not otherwise doable on pure unrooted stock. FWIW, if you are rooted, you can use @flar2's ElementalX kernel which is quite good, especially when used with the helper app allowing you to tweak all settings.
Summary && Detail:
1, you can convert the application to VR mode to watch and operate.
2, support the Bluetooth handle.
3, VR mode to support the up and down volume keys to control the screen size.
4, support touch screen operation, touch screen area from the upper left corner of the physical screen to start mapping
5, there may be some BUG, disable module can be restored
ScreenShot && Download:
http://repo.xposed.info/module/com.app360.app360
YOUTUBE:
https://www.youtube.com/watch?v=qyROy_zLaQA
Major update!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
detail:
Support global VR mode in landscape for all of android apps.
This function is tested on Android 5.1 and Android 6, Android5.0 has not yet tested.
This function is strong enough for having no friends
using:
open settings app,find Accessibility,switch on Magnification gestrues.when play apps in landscape,triple tapping the screen,then you will in VR mode.
notice:
miui should allow system alert window
if not work,please check auto run and record screen permission
any suggesting can email to [email protected]
app2vr said:
Summary && Detail:
1, you can convert the application to VR mode to watch and operate.
2, support the Bluetooth handle.
3, VR mode to support the up and down volume keys to control the screen size.
4, support touch screen operation, touch screen area from the upper left corner of the physical screen to start mapping
5, there may be some BUG, restart the phone can be restored
ScreenShot && Download:
repo.xposed.info/module/com.app360.app360
Click to expand...
Click to collapse
Wow is this real ?! I always wanted to do that
I'm testing it on a nexus 6. I'll report bug with logs if needed
thank you !!!!
BUG
Well it's not working on nexus 6 for me. It shows a dark screen when launching an app through app2vr interface.
Logs attached
also why so many files comes on /sdcard after instalation?? It looks like malicious app...
Dead-neM said:
Wow is this real ?! I always wanted to do that
I'm testing it on a nexus 6. I'll report bug with logs if needed
thank you !!!!
BUG
Well it's not working on nexus 6 for me. It shows a dark screen when launching an app through app2vr interface.
Logs attached
also why so many files comes on /sdcard after instalation?? It looks like malicious app...
Click to expand...
Click to collapse
Hi,thank you very much,because my application supports xposed mode and normal root mode, so i need to release the GoogleDoor and Lib files in sdcard for injection into the system_server process to complete the functional patch, the program does not contain malicious code, you can decompile to confirm, according to your feedback Log, I modified the program, the current xposed mode does not need to click to install, activate the module can be used after the restart, this is the beta version, does not support all types of app to be converted into vr mode,the current upgrade to the 19 version,this version had repaired your feedback.
app is really available
app is really available, but in the early stages of development, I will be the fastest speed to solve the problem.
Zenfone2 ze331ml lollipop 5.0.1 here.
Installed, allowed root to modify system partition, tried to start 920 text editor and just got a black screen.
Phone did not react to nothing, home button, power button, nothing. seems dead.
After a while adb via usb started working, and i issued a reboot from there.
Next, i've got a bootloop; i disabled xposed and the bootloop did not went away!
Fortunately i've had a complete twrp backup...
I tried to understand what it did to my system app, but the source on github is not available.
app2vr said:
Hi,thank you very much,because my application supports xposed mode and normal root mode, so i need to release the GoogleDoor and Lib files in sdcard for injection into the system_server process to complete the functional patch, the program does not contain malicious code, you can decompile to confirm, according to your feedback Log, I modified the program, the current xposed mode does not need to click to install, activate the module can be used after the restart, this is the beta version, does not support all types of app to be converted into vr mode,the current upgrade to the 19 version,this version had repaired your feedback.
Click to expand...
Click to collapse
Hi, thanks for the app
U mentioned about root mode. Any case this works with nougat in root mod I'm just asking
app2vr said:
Hi,thank you very much,because my application supports xposed mode and normal root mode, so i need to release the GoogleDoor and Lib files in sdcard for injection into the system_server process to complete the functional patch, the program does not contain malicious code, you can decompile to confirm, according to your feedback Log, I modified the program, the current xposed mode does not need to click to install, activate the module can be used after the restart, this is the beta version, does not support all types of app to be converted into vr mode,the current upgrade to the 19 version,this version had repaired your feedback.
Click to expand...
Click to collapse
Awesome I'll try again and report back. Thank you for being super fast.
Just one question what is the demo.apk on /sdcard?
When I try opening an application, a black screen just shows any way I can fix this? I am on a Redmi Note 3.
Dead-neM said:
Awesome I'll try again and report back. Thank you for being super fast.
Just one question what is the demo.apk on /sdcard?
Click to expand...
Click to collapse
DemoInject2.apk contains the function code,processing function logic in native layer is very complicated ,processing in java layer by using dexclassloader can enhance the stability.thanks
kokoko3k said:
Zenfone2 ze331ml lollipop 5.0.1 here.
Installed, allowed root to modify system partition, tried to start 920 text editor and just got a black screen.
Phone did not react to nothing, home button, power button, nothing. seems dead.
After a while adb via usb started working, and i issued a reboot from there.
Next, i've got a bootloop; i disabled xposed and the bootloop did not went away!
Fortunately i've had a complete twrp backup...
I tried to understand what it did to my system app, but the source on github is not available.
Click to expand...
Click to collapse
Very sorry,its my fault, I am tested on Android 5.1, Android6.0 machine, can you provide some log information? MainXposed.java is not confused, because the visual processing part of the code is not my work,so its hard to opensource.
reversegear said:
Hi, thanks for the app
U mentioned about root mode. Any case this works with nougat in root mod I'm just asking
Click to expand...
Click to collapse
Today, I experimented with Android N, I found that when I injected into the system_server, android :: AndroidRuntime :: getJavaVM () often return null ,so i can not load the function code in DemonInject.apk with jni_env , i am looking for solution..
APP2VR now can run on nougat when selinux disabled.
Gtxinsane said:
When I try opening an application, a black screen just shows any way I can fix this? I am on a Redmi Note 3.
Click to expand...
Click to collapse
can you provider me some log? I will resolve your problem as quickly as possible!
On v20 it's still not working on a nexus6. Problem looks the same. Video and Logs below.
https://drive.google.com/folderview?id=0BwCC2VJYgCavdzUyODhjejAtZXM
waiting for stable build
Dead-neM said:
On v20 it's still not working on a nexus6. Problem looks the same. Video and Logs below.
https://drive.google.com/folderview?id=0BwCC2VJYgCavdzUyODhjejAtZXM
Click to expand...
Click to collapse
From the Log analysis, APP2VR Xposed Module is not enabled, I Hooked startActivity but no log output, you can uninstall and reinstall V21 version.
app2vr said:
From the Log analysis, APP2VR Xposed Module is not enabled, I Hooked startActivity but no log output, you can uninstall and reinstall V21 version.
Click to expand...
Click to collapse
Why no suports phone root
After “put your device into cardboard“ just a black screen with the settings symbol, but not clickable + difficulties exiting the app.
InFocus M808 modded Stock 6.0
Could you include two key options.
1. To disable gyroscope, or to show in static frame.
2. To adjust FOV.
Sent from my Lenovo X3a40 using XDA Labs
BUGS
In Cardboard mode: It only shows main activity, app can not be controlled by the headset, Moga gamepad doesnt work (moga universal driver) and probably other controllers, and yoi have to look towards fixed direction
In Global mode: Not all the screen is visible through the vr glass (bigger than it should be)
please support locked mode screen
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.
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.
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