[OP8P] PhotoChrom enabled - Without PC - Non Root - OnePlus 8 Pro Themes, Apps, and Mods

Hello everyone.
This is a guide to enable the Photochrom camera without using a PC.
Steps:
1. Install Termux - https://play.google.com/store/apps/details?id=com.termux&hl=en&gl=US
2. Run this command on Termux:
apt update > /dev/null 2>&1 && apt --assume-yes install wget > /dev/null 2>&1 && wget https://github.com/MasterDevX/Termux-ADB/raw/master/InstallTools.sh -q && bash InstallTools.sh
Wait for a while and let this command complete. (Needs internet connected)
3. Run this command in Termux:
adb devices
4. Go to developers settings. We need to change 3 settings:
First turn all of them off:
a) Wireless debugging
b) Wireless ADB debugging
c) USB debugging
Now you have to turn them on in this order (Yes the order is important)
a) Wireless debugging (Also click allow on prompt)
b) Wireless ADB debugging
c) USB debugging (Also click allow on prompt)
5. Go back to Termux and type:
Adb devices
You phone should show up with the IP
6. In termux run:
Adb shell
and then run:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
CONGRATS!! The camera runs now.
Change camera to camera 4. This is the photochrom camera.
Now go to recent apps and lock this camera app.
Now you never have to worry again.
This app will always be available in recent apps.
EXTRA STEP. If "adb shell" command does not run.
You need to do one extra step after step 5
5.5. If your ip is 192.168.2.3:5555
run this command
adb connect 192.168.2.3:5555
then do step 6
DOESN'T WORK?
Uninstall Termux and repeat procedure again. Follow the video attached.
VIDEO TUTORIAL
For Video Tutorial please follow the link
2020_12_06_19_06_32.mp4
drive.google.com

Hi mate, great job. But I have a doubt, if I follow all the steps my stock camera version will still be the newest? or do I go back to an older version?

Zokinet said:
Hi mate, great job. But I have a doubt, if I follow all the steps my stock camera version will still be the newest? or do I go back to an older version?
Click to expand...
Click to collapse
You stock camera will not be changed

This works fabulous on OnePlus 8 pro IN2021 running Android 11.0.2.2 thanks again.

Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.

iamtalha said:
You stock camera will not be changed
Click to expand...
Click to collapse
Thanks, All works good.
Good job.

I'm not getting an ip address in Step 5, so termux doesn't see my device. I turned on those settings in order...

Rajul said:
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
That means your "adb shell" command didn't work, or you did not use that command. Please watch the video I just attached to the original post

GatorsUF said:
I'm not getting an ip address in Step 5, so termux doesn't see my device. I turned on those settings in order...
Click to expand...
Click to collapse
Please check the video I just attached.

Good video : cheers

Awesome, this works fine on OOS 11 stable. Thanks a lot.

Rajul said:
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
You need to disable all your magisk modules to use it.
Tried, no x ray effect

I am not even rooted
Svid said:
You need to disable all your magisk modules to use it.
Tried, no x ray effect
Click to expand...
Click to collapse

iamtalha said:
That means your "adb shell" command didn't work, or you did not use that command. Please watch the video I just attached to the original post
Click to expand...
Click to collapse
Will it work on oos 10?

Rajul said:
Will it work on oos 10?
Click to expand...
Click to collapse
Not sure. But it should

Svid said:
You need to disable all your magisk modules to use it.
Tried, no x ray effect
Click to expand...
Click to collapse
Xray effect is very slight. It is just hyped

OP8Pro, A11, running shell as su was required or else I would get the message:
"Warning: Activity not started because the current activity is being kept for the user."
App launched, but error message popped up, image attached
After disabling xXx NoLimits Magisk Module, the photochrome camera worked!

oSumAtrIX said:
OP8Pro, A11, running shell as su was required or else I would get the message:
"Warning: Activity not started because the current activity is being kept for the user."
App launched, but error message popped up, image attached
After disabling xXx NoLimits Magisk Module, the photochrome camera worked!
Click to expand...
Click to collapse
Yes this method was for non rooted phones. Rooted phones have other better methods

For anyone trying this on OOS 10, it will not work for non rooted oos 10 as the factory mode feature was disabled by OnePlus in latest Stable update but it works for OOS 11 stable.(as of now)

iamtalha said:
Xray effect is very slight. It is just hyped
Click to expand...
Click to collapse
Well this guide does work for me 11.0.2.2 BA but the hype i had was big lol

Related

[GUIDE] Install fleksy keyboard on any android wear with ADB

hi guys, i try to install some querty keyboard like fleksy on android wear with adb comands.
after many attemps i found the way.
You should be having android platflorm Tools to use ADB.
1. Enable Android Debugging in your android wear (tap many times on build version)
2. Connect your android wear watch.
3. connect your smartwatch to phone via bluetooth
4.write: adb devices
5. see if your device is listed (if you see "unhautorized" see your smartphone to allow the permission)
6.Install App to your watch using this Command: adb install yourApkName.apk
7.Type: adb shell ime enable com.syntellia.fleksy.kb/.Fleksy (if this give you an error try com.syntellia.fleksy.keyboard/.Fleksy)
8.Type: adb shell ime set com.syntellia.fleksy.kb/.Fleksy (if this give you an error try com.syntellia.fleksy.keyboard/.Fleksy)
Done.
If i help you press thanks
fer2503 said:
hi guys, i try to install some querty keyboard like fleksy on android wear with adb comands.
after many attemps i found the way.
You should be having android platflorm Tools to use ADB.
1. Enable Android Debugging in your android wear (tap many times on build version)
2. Connect your android wear watch.
3. connect your smartwatch to phone via bluetooth
4.write: adb devices
5. see if your device is listed (if you see "unhautorized" see your smartphone to allow the permission)
6.Install App to your watch using this Command: adb install yourApkName.apk
7.Type: adb shell ime enable com.syntellia.fleksy.kb/.Fleksy (if this give you an error try com.syntellia.fleksy.keyboard/.Fleksy)
8.Type: adb shell ime set com.syntellia.fleksy.kb/.Fleksy (if this give you an error try com.syntellia.fleksy.keyboard/.Fleksy)
Done.
If i help you press thanks
Click to expand...
Click to collapse
I think its great idea, but whenever i try enabling it i get error. I tried changing lines a little bit in sooo many ways but never got "Succes". Most often i got id:null ;/
Lasiu said:
I think its great idea, but whenever i try enabling it i get error. I tried changing lines a little bit in sooo many ways but never got "Succes". Most often i got id:null ;/
Click to expand...
Click to collapse
ok no problem. the problem is that the file package (com.example....) depends on your apk file. So you can do this:
-download this application for windows: apk tool for wear from xda
-connect to your phone
-find in the list the name of your fleksy package (com.syntellia....)
-write it in the adb command. (example: adb shell ime enable "yourpackage"/.Fleksy )
fer2503 said:
ok no problem. the problem is that the file package (com.example....) depends on your apk file. So you can do this:
-download this application for windows: apk tool for wear from xda
-connect to your phone
-find in the list the name of your fleksy package (com.syntellia....)
-write it in the adb command. (example: adb shell ime enable "yourpackage"/.Fleksy )
Click to expand...
Click to collapse
My package's name was same as yours (i checked it ) Any other recommendations? Or do you mean, that i should try enabling keyboard through this tool? Though i didnt see this option when i downloaded it week ago or something
Lasiu said:
My package's name was same as yours (i checked it ) Any other recommendations? Or do you mean, that i should try enabling keyboard through this tool? Though i didnt see this option when i downloaded it week ago or something
Click to expand...
Click to collapse
The tool is only to see the exatly package name. Czn you make a screenshot of your adb command with error and the package name showed in apk tool?
fer2503 said:
The tool is only to see the exatly package name. Czn you make a screenshot of your adb command with error and the package name showed in apk tool?
Click to expand...
Click to collapse
See My apk name is: com.syntellia.fleksy.kb.apk Any ideas? ;/
Lasiu said:
See My apk name is: com.syntellia.fleksy.kb.apk Any ideas? ;/
Click to expand...
Click to collapse
The package name, not the apk name. Post the screenshot of the apktool package list.
fer2503 said:
The package name, not the apk name. Post the screenshot of the apktool package list.
Click to expand...
Click to collapse
Is that what you mean?
Lasiu said:
Is that what you mean?
Click to expand...
Click to collapse
I think that the problem is the /.Fleksy...maybe you can try /.Fleksy.kb or /.Fleksykb
fer2503 said:
I think that the problem is the /.Fleksy...maybe you can try /.Fleksy.kb or /.Fleksykb
Click to expand...
Click to collapse
No luck Maybe something like FleksyKeyboardService? Other keyboards have that in their line, though i tried it and it didnt work. I will try again. Any more ideas?
fer2503 said:
I think that the problem is the /.Fleksy...maybe you can try /.Fleksy.kb or /.Fleksykb
Click to expand...
Click to collapse
Yep it doesnt work. Btw can you post photos of your Smartwatch with this keyboard?
Lasiu said:
Yep it doesnt work. Btw can you post photos of your Smartwatch with this keyboard?
Click to expand...
Click to collapse
+1 I would like to see as well
Lasiu said:
Yep it doesnt work. Btw can you post photos of your Smartwatch with this keyboard?
Click to expand...
Click to collapse
Yes i can make a photo and post it to you. It is too small but it works
yyeah a picture would be cool

Need help spoofing MAC address on my Amazon Fire (Cyanogenmod 12.1)

I have an Amazon Kindle Fire 7 inch 5th generation tablet running the unofficial build of Cyanogenmod 12.1 for this device (main thread). I've got root, I'm running without GApps, and my setup is working great. The only thing I have yet to resolve is that I cannot spoof my MAC address. If I try to do so with something like:
Code:
su
busybox ifconfig wlan0 down
busybox ifconfig wlan0 hw ether 00:11:22:33:44:55
busybox ifconfig wlan0 up
it will fail on "busybox ifconfig wlan0 hw ether 00:11:22:33:44:55" with the message:
Code:
ifconfig: SIOCSIFHWADDR: Operation not supported on transport endpoint
I also tried two similar approaches:
Code:
su
busybox ifconfig wlan0 down && macchanger -r wlan0
fails with
Code:
[ERROR] Could not change MAC: interface up or insufficient permissions: Operation not supported on transport endpoint
while
Code:
su
ip link set wlan0 address 00:11:22:33:44:55
fails with:
Code:
RTNETLINK answers: Operation not supported on transport endpoint
From the googling I have done, it seems that this may be due to a limitation of the hardware, kernel or wifi drivers? Hopefully that doesn't mean there is nothing I can do and nothing more to try. Are there perhaps other methods that would bypass this problem?
For a bit of additional info, the application "Dalvik Explorer" shows under device details "Hardware: MT8127", which I hope is a useful piece of information to someone with more technical expertise than me. If it is a driver issue, are there perhaps newer drivers for that I could manually load somehow? If it is a kernel issue, is there anything I can do to modify the kernel (not something I have the slightest bit of experience with, but I'll be damned if I can't try). Any guidance or ideas would be extremely helpful.
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
ggow said:
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
Click to expand...
Click to collapse
Aw.
Well, thanks for letting me know. And thank you for bringing Cyanogenmod to this device, I have been enjoying it greatly!
ggow said:
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
Click to expand...
Click to collapse
cyanogen_aw_yeah said:
Aw.
Well, thanks for letting me know. And thank you for bringing Cyanogenmod to this device, I have been enjoying it greatly!
Click to expand...
Click to collapse
Unless Amazon has deprecated this (e.g. with a kernel update?),
on my 2015 Fire + CM12.1 (per OP's link) I'm able to spoof my MAC address using the idme command.
Code:
su -c idme mac_addr 38aa3c123456
su -c idme print mac_addr # check to see that it set it
Then restart the device. After rebooting, go to CM Wi-Fi settings -> Advanced and see if it worked. It seems certain OUIs (first half) are rejected by the OS.
I found this while poking through the kernel code earlier this year. But per @ggow's comment, maybe they've nixed it since then.
Working On FireHD 10 2017
jrodat said:
Unless Amazon has deprecated this (e.g. with a kernel update?),
on my 2015 Fire + CM12.1 (per OP's link) I'm able to spoof my MAC address using the idme command.
Code:
su -c idme mac_addr 38aa3c123456
su -c idme print mac_addr # check to see that it set it
Then restart the device. After rebooting, go to CM Wi-Fi settings -> Advanced and see if it worked. It seems certain OUIs (first half) are rejected by the OS.
I found this while poking through the kernel code earlier this year. But per @ggow's comment, maybe they've nixed it since then.
Click to expand...
Click to collapse
I can confirm this is working on my fire hd 10 2017!!! You have made my day I wish you the best of luck in life!!!
AustinR66 said:
I can confirm this is working on my fire hd 10 2017!!! You have made my day I wish you the best of luck in life!!!
Click to expand...
Click to collapse
Hi can you tell me how to do this i want to do it on a fire 7 do i need root access? If so what do i need to install and where do i type these idme commands? Sorry bit of a noob to all this.
saupe2005 said:
Hi can you tell me how to do this i want to do it on a fire 7 do i need root access? If so what do i need to install and where do i type these idme commands? Sorry bit of a noob to all this.
Click to expand...
Click to collapse
Hey,
If you have Cyanogenmod, you should be able to do it without installing anything.
These directions are for my Fire 7 2015. Screenshots included at the bottom.
Go to your Settings app and click "About tablet"
Find the line that says "Build number" and tap repeatedly on it. Eventually it will say "Developer settings unlocked" (or something like that).
Now go back to the main Settings page and open "Developer options". On this page you must enable 2 things:
"Root access" - enable this for 'apps'
"Local terminal" - enable this too.
Then reboot the device.
(This is needed for enabling root access.)
The Terminal app may not show directly on your launcher, but you will see it if you list all your apps.
Open the Terminal app, and enter the following commands, on separate lines:
Code:
su
idme mac_addr 4c0b3a000002
idme print mac_addr
(The "su -c" version wasn't working for me with the built-in Terminal app, I had to enter "su" by itself)
- The first line ("su") may show a popup asking you to confirm Root access
- The second line should display to your screen "Writing idme data..."
- The third line prints the mac address to make sure you set it successfully.
After this, you must reboot your device, to activate the new MAC address.
Sometimes the kernel will ignore the new mac, if the first 6 chars (the oui) are unrecognized. The prefixes "4c0b3a" and "38aa3c" both work for me. Or you can use the 6 chars that are built-in for your device. (run the "idme print mac_addr" line to see what they are.)
A mac address is all Hex chars, so only 0-9 and A-F are valid characters.
Check your Wi-Fi settings -> Advanced to make double-sure that it worked.
Hope this helps
Here are the screenshots (Click to zoom)
jrodat said:
Hey,
If you have Cyanogenmod, you should be able to do it without installing anything.
Thanks for your reply.
I dont seem to have the same options as you i have a fire 7, 7th gen i have managed to enable developer options by tapping my serial number but dont see any options about root access any ideas?
Click to expand...
Click to collapse
saupe2005 said:
I dont seem to have the same options as you i have a fire 7, 7th gen i have managed to enable developer options by tapping my serial number but dont see any options about root access any ideas?
Click to expand...
Click to collapse
The instructions were for Cyanogenmod OS 12.1 (thread title), that could be why it looks different.
I should've paid attention when you said "7th gen", my bad. I didn't realize, there's no way to root the 7th gen yet (or install a custom ROM):
https://forum.xda-developers.com/am...th-gen-2017ask-question-t3636919#post73033591
If/when someone cracks it, basically what you would need is a Terminal app from the Play Store, and root. Then the rest of the steps should work.
sorry about that :/
jrodat said:
The instructions were for Cyanogenmod OS 12.1 (thread title), that could be why it looks different.
I should've paid attention when you said "7th gen", my bad. I didn't realize, there's no way to root the 7th gen yet (or install a custom ROM):
https://forum.xda-developers.com/am...th-gen-2017ask-question-t3636919#post73033591
If/when someone cracks it, basically what you would need is a Terminal app from the Play Store, and root. Then the rest of the steps should work.
sorry about that :/
Click to expand...
Click to collapse
You gotta root it but if there is no root available then your out of luck. Sorry mate.

[DEV][PACE/STRATOS] Android Wear Framework

...and not WearOS because this is from an Android 5.1.1 build from 2015
I talked about the Wear framework in this thread, and how it can be partially installed onto the Pace and Stratos
THIS DOES NOT MEAN A FULLY WORKING ANDROID WEAR BUILD!
It doesn't connect to the Wear app, even after installing all the APKs required and following the correct setup procedure (some bluetooth error, even after patching it with the supposed workaround for normal apps, it doesn't work - maybe the Bluetooth stack on these watches doesn't work for Wear)
What it does allow is for standalone wear apps with really simple functions to work. Good examples of this are Wear Bottle Spinner (eliseo.wearbottlespinner.wear) and Interval timer for Android Wear (wearablesoftware.wearintervaltimer), which on this list are "not working" due to lack of wear framework, but work after these files have been copied.
Please do not attempt this if you want a fully stable device, or don't feel comfortable debugging. It may not work for you, and you may end up having to post crash logs or have a not-working device. This is a development thread, it's not fully ready for use yet
Installation
- Download this zip
- Extract it and run the following commands from the folder
Code:
adb root
adb remount
adb push com.google.android.wearable.jar /system/framework
adb push clockwork-system.jar /system/framework
adb push com.google.android.wearable.xml /system/etc/permissions
adb push clockwork-system.xml /system/etc/permissions
adb push ClockworkAmbient.apk /system/priv-app/ClockworkAmbient/ClockworkAmbient.apk
adb reboot
I think this is all that's needed for it to work. My test device has more Wear framework APKs on it than are needed, so I'm not totally sure. If it crashes after doing this, please post a logcat and I'll see if anything else is needed - that's why this is a DEV thread!
These files were taken from the last Android 5.1.1 Wear build for the Gear 2 (itself a port): https://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
From having followed the AW porting thread for the Samsung Gear S back in the days I can say the following things:
The Bluetooth stack is indeed different between normal Android and Android Wear but IIRC it should be at least theoretically possible to make it work unless Xiaomi/Huami modified it.
To connect to the AW app it will also require to have all the AW GAPPS properly setup AND the fingerprint of a watch it will recognize with said AW version, even an AW port just won't connect with the app unless there is a proper fingerprint setup in build.prop
On another note great job on doing this and I will be testing it out later today when I will have some free time and an easy way of getting said AW apps.
Hello Quinny, I think you're doing a great job, and it's appreciated. What is the scope of this? I am clear that we will not see Android Wear on our devices, but can Google services and applications be installed? Or would it only be used to install certain applications?
Thanks for your contributions.
zodrac said:
Hello Quinny, I think you're doing a great job, and it's appreciated. What is the scope of this? I am clear that we will not see Android Wear on our devices, but can Google services and applications be installed? Or would it only be used to install certain applications?
Thanks for your contributions.
Click to expand...
Click to collapse
It's to make apps that rely on the Wear framework classes work, but only those that are standalone
Ranomez said:
From having followed the AW porting thread for the Samsung Gear S back in the days I can say the following things:
The Bluetooth stack is indeed different between normal Android and Android Wear but IIRC it should be at least theoretically possible to make it work unless Xiaomi/Huami modified it.
To connect to the AW app it will also require to have all the AW GAPPS properly setup AND the fingerprint of a watch it will recognize with said AW version, even an AW port just won't connect with the app unless there is a proper fingerprint setup in build.prop
On another note great job on doing this and I will be testing it out later today when I will have some free time and an easy way of getting said AW apps.
Click to expand...
Click to collapse
@Quinny899 what do you think, would it be possible?
Hi, will this work with this?
https://play.google.com/store/apps/details?id=prox.lab.calclock&hl=cs
urbami said:
Hi, will this work with this?
https://play.google.com/store/apps/details?id=prox.lab.calclock&hl=cs
Click to expand...
Click to collapse
No
Hello there! I think you are doing a fanstastic job! But I have a problem, I can't do adb remount... It says permission denied. Any help is appreciated
Qufy said:
Hello there! I think you are doing a fanstastic job! But I have a problem, I can't do adb remount... It says permission denied. Any help is appreciated
Click to expand...
Click to collapse
You need to be running a rooted boot image and have successfully run "adb root" before remount.
Quinny899 said:
You need to be running a rooted boot image and have successfully run "adb root" before remount.
Click to expand...
Click to collapse
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Qufy said:
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Click to expand...
Click to collapse
What does adb root return? Can you send a screenshot?
Quinny899 said:
What does adb root return? Can you send a screenshot?
Click to expand...
Click to collapse
It returns nothing so I am not sure :/
https://imgur.com/TUeo3ky
Qufy said:
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Click to expand...
Click to collapse
You have to boot (not flash) an boot image with root support and run the commands directly then.
Do a search for root Amazfit, there are some guides.
GreatApo said:
You have to boot (not flash) an boot image with root support and run the commands directly then.
Do a search for root Amazfit, there are some guides.
Click to expand...
Click to collapse
I will try that thanks
Qufy said:
It returns nothing so I am not sure :/
https://imgur.com/TUeo3ky
Click to expand...
Click to collapse
Nothing = it didn't work.
If it works it says "adbd restarting as root"
Quinny899 said:
Nothing = it didn't work.
If it works it says "adbd restarting as root"
Click to expand...
Click to collapse
Oh ok thanks
Quinny899 said:
...and not WearOS because this is from an Android 5.1.1 build from 2015
I talked about the Wear framework in this thread, and how it can be partially installed onto the Pace and Stratos
THIS DOES NOT MEAN A FULLY WORKING ANDROID WEAR BUILD!
It doesn't connect to the Wear app, even after installing all the APKs required and following the correct setup procedure (some bluetooth error, even after patching it with the supposed workaround for normal apps, it doesn't work - maybe the Bluetooth stack on these watches doesn't work for Wear)
What it does allow is for standalone wear apps with really simple functions to work. Good examples of this are Wear Bottle Spinner (eliseo.wearbottlespinner.wear) and Interval timer for Android Wear (wearablesoftware.wearintervaltimer), which on this list are "not working" due to lack of wear framework, but work after these files have been copied.
Please do not attempt this if you want a fully stable device, or don't feel comfortable debugging. It may not work for you, and you may end up having to post crash logs or have a not-working device. This is a development thread, it's not fully ready for use yet
Installation
- Download this zip
- Extract it and run the following commands from the folder
Code:
adb root
adb remount
adb push com.google.android.wearable.jar /system/framework
adb push clockwork-system.jar /system/framework
adb push com.google.android.wearable.xml /system/etc/permissions
adb push clockwork-system.xml /system/etc/permissions
adb push ClockworkAmbient.apk /system/priv-app/ClockworkAmbient/ClockworkAmbient.apk
adb reboot
I think this is all that's needed for it to work. My test device has more Wear framework APKs on it than are needed, so I'm not totally sure. If it crashes after doing this, please post a logcat and I'll see if anything else is needed - that's why this is a DEV thread!
These files were taken from the last Android 5.1.1 Wear build for the Gear 2 (itself a port): https://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
Click to expand...
Click to collapse
Can it delete my ROM(PACEfied)?
Hi is it possible to run google fit directly from watch?
With framewotk or any custom build google fit apk? Anyone test it?
Will the application like a "com.huami.watch.deskclock" and another stock application still works ?
A M A Z F I T S T R A T O S
lensSGzaza said:
Will the application like a "com.huami.watch.deskclock" and another stock application still works ?
A M A Z F I T S T R A T O S
Click to expand...
Click to collapse
Yes.

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.

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