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
Related
Announcing Sailfish for the Sony Xperia SP
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Update 15 Feb 2016
I've uploaded a new version of SailfishOS 2.0.0.10 to the Mega folder, called sailfishos-huashan-release-2.0.0.10-1.zip. This is again based off CM-12.1, the same release as stated below. This release fixes a kernel bug which lets a lot of the Sailfish system crash. This also fixes the wlan connectivity, startup-wizard which sets the themes, on-screen keyboard not popping up, and SIM unlock never asked. I've got a fix for the backlight in the works.
Update 14 Feb 2016
A very experimental CM-12.1 based SailfishOS 2.0.0.10 build is uploaded to the Mega folder linked below.
This version is based off cm-12.1-20160212-NIGHTLY-huashan.zip. I want to stress that many things in this build are broken.
Update 05 Feb 2016
This port is heavily outdated. I do not have much spare time on my hands to continue porting but I will try to post a nightly version soon.
This version was based on Sailfish 1.1.6 and CM-11.0, but the world has moved on to Sailfish 2.0 and CM-12.1, and so must this port.
There's a photo up on imgur:
http://i.imgur.com/Vg3SZ6w.jpg
Special thanks to:
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Everyone from the SailfishOS team/community, sledges and mal- in particular.
Known issues:
Half the backlight doesnt work, this is clearly visible at the top of the screen
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Settings hangs for few seconds on first start (this seems to be related to bluetooth not being set up)
What works:
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi, GPS (does take a while to get a fix though), most of the sensors (proximity, lightsensor etc)
The half of the display backlight that does work is adjusted based on lightsensor input.
Charging, bottom ledbar basic functionality, audio works, audio via 3'5 jack also works.
Installation:
Insert default warranty void message here. Your warranty is now void
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an offical Sailfish OS build, and the Xperia SP is not the Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, search for it first on bit.ly/port-bugs, if your bug is not yet there, you can add it there or post it in this thread (I'll try to keep the xda thread and bugzilla in sync).
The Sailfish OS image does not provide recovery, and since the Xperia SP does not have a recovery partition, you need a seperate bootimage with only recovery on it to flash cm/stock/sailfishos upgrade.
The Sailfish OS image is based on a specific version of Cyanogenmod 11, which you will need to flash first.
You can find all the required files in a Mega folder: http://mega.nz/#F!7YhSTDIA!Akpjs8s3qT5_nEkN04fQ-Q
You can find a bootimage with only TWRP recovery in it called recoveryboot.img
This image can be flashed with fastboot (with phone turned off, hold vol up and plug in usb), then `fastboot flash boot recoveryboot.img`. After that reboot the phone (fastboot reboot), and it will boot into recovery. If you already have recovery from cm, then you can use that as well.
First do a full wipe (make a backup first if needed, TWRP can do this , then install CM11, the specific version you need is called: cm-11-20150712-NIGHTLY-huashan.zip
There is no need to reboot cause you wont use CM11 anyway, so just proceed and flash the Sailfish OS image, which is called: sailfishos-huashan-release-1.1.6.27-UNOFFICIAL-maikel-201508201214.zip
Flashing Sailfish OS is not as fast as flashing cm11, but it shouldn't take more than 10 minutes.
Then reboot. The first boot may take some time, during which the Sony logo is not displayed (WIP).
If the boot takes more than, lets say five minutes, try a reboot. You can power off the device by holding the power button until the LED bar turns red or the display brightness goes back to full, when the leds and display turn off the device is powered off.
If this doesn't work you can remove the back cover and press the little button in the little hole for 5 seconds, the device will vibrate thrice and the phone will be forced off.
If you want to return to your previous rom or restore a backup, use the recoveryboot.img using the commands stated at the top of this document, to boot into TWRP.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Sources
In order to comply with the GPL, the kernel sources used for this port are available here:
CM-11.0 based port: https://github.com/maikelwever/android_kernel_sony_msm8x60
CM-12.1 based port: https://github.com/maikelwever/android_kernel_sony_msm8960t
edit: make links + sailfish 2.0 notice, kernel sources, 2.0 link
You rock! Very interesting project. Sailfish is an unknown world for me (and for most of us I think), I might try this ROM out sooner or later.
Why do we need to install CM11 first? Is it based on it?
Goob job bro!!!!
But I'll try this port later since it's kinda buggy
Hope you will fix those bugs.
Tomoms said:
Why do we need to install CM11 first? Is it based on it?
Click to expand...
Click to collapse
SailfishOS uses libhybris to communicate with the hardware, which in turn is talking to the Android HAL (like hwcomposer), to avoid having to write drivers for each phone, which would be pretty much impossible due to the proprietary blobs used on almost every phone.
The libhybris build included in this SailfishOS port is based on CM11, so that's why you need that.
CM12 based SailfishOS is currently experimental, when that gets more stable I will try to make a CM12 based build.
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
boylush said:
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
Click to expand...
Click to collapse
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
maikoool said:
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
Click to expand...
Click to collapse
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Tomoms said:
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Click to expand...
Click to collapse
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
maikoool said:
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
Click to expand...
Click to collapse
man i was waiting for this thing :fingers-crossed:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
will follow this thread closely...........
finally something new and different to use.
cheers
avi.singh9993 said:
will follow this thread closely...........
finally something new and different to use.
cheers
Click to expand...
Click to collapse
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
This looks really good, if it will ever be in daily driver state this will be my go to rom
sledges said:
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
Click to expand...
Click to collapse
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Why don't you post please? DIT - doing it together!
sledges said:
Why don't you post please? DIT - doing it together!
Click to expand...
Click to collapse
well i asked my friend to post it,
many people saw it but unfortunately not much of a positive feedback.
now it's onto developer and his hardwork to develop and make it atleast daily driver. then some people will be interested in trying it
Tomoms said:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
Click to expand...
Click to collapse
I agree totally that it's the dream of a geek. I've noted all your comments and will try to fix them. Thank you very much for taking the time to test!
Spasik said:
This looks really good, if it will ever be in daily driver state this will be my go to rom
Click to expand...
Click to collapse
That's what I'm aiming for too!
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Sorry, but I couldn't care less about Facebook. I'm pretty convinced that everyone that is willing to try something like this is already on XDA anyway. Hopefully the work related part will be better possible when Android app emulation or something similar finally makes it to community Sailfish builds.
PS: I've been a bit busy with other things lately, sorry for not responding that fast. I'll try to roll a build with fixes and the latest Sailfish (1.1.7.28) asap.
This has changed the mac of my device
can I ask how's the development going?
If someone could port the only rom i would like to be ported on the SP: ColourOS, it will be AMaZING
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.
Yeah,you heard it right!
The long awaited feature,ability to map keys for games that are originally developed for touchscreen enabled devices are coming to RemixOs.
The chinese version of RemixOs has a new version (2.0.401) dated 27th June 2016,which claims to support keymapping.
You can check the changelog at https://bbs.jide.com/forum.php?mod=viewthread&tid=7351
I wanted to give it a try.but the download was stucked due to the low bandwith offered by server,unfortunately.
If you are brave enough to take a early look,or can't wait for the global release. here are the download links.
1) http://pan.baidu.com/s/1bpibhZT
Code: gbku
2) https://yunpan.cn/OcRUtwhPNKenuX
Code: 938d
PS: Those files are hosted in chinese servers,so the bandwith is not super high. You're on your own,and ask google translate for help
Thisu said:
Yeah,you heard it right!
The long awaited feature,ability to map keys for games that are originally developed for touchscreen enabled devices are coming to RemixOs.
The chinese version of RemixOs has a new version (2.0.401) dated 27th June 2016,which claims to support keymapping.
You can check the changelog at https://bbs.jide.com/forum.php?mod=viewthread&tid=7351
I wanted to give it a try.but the download was stucked due to the low bandwith offered by server,unfortunately.
If you are brave enough to take a early look,or can't wait for the global release. here are the download links.
1) http://pan.baidu.com/s/1bpibhZT
Code: gbku
2) https://yunpan.cn/OcRUtwhPNKenuX
Code: 938d
PS: Those files are hosted in chinese servers,so the bandwith is not super high. You're on your own,and ask google translate for help
Click to expand...
Click to collapse
use the baidu link . download speed is ok
enter the code :gbku in the box before 提取文件. press enter.
click the file Remix OS PC版(64位). then put a tick on the box for the zip file and md5 file . now click on 下载 to download.
if you want to use alt+f1 , you need to go to setting , then experimental , you can enable alt+f1 there .
you need this to enable google play store
if you want root just replace the su file under system/xbin
tested working in virtualbox and harddisk
Ok, very nice and all but...will it support my nvidia card with the official nvidia driver?
or29544 said:
Ok, very nice and all but...will it support my nvidia card with the official nvidia driver?
Click to expand...
Click to collapse
it work fine on gtx 750 ti. there is only the open source driver no official nvidia driver.
I thought the next update would be 3.0......
The forum link isn't opening.. can u copy th changelog here?
modaifallah said:
The forum link isn't opening.. can u copy th changelog here?
Click to expand...
Click to collapse
Google Translate version of this page - https://bbs.jide.com/forum.php?mod=viewthread&tid=7351
Remix OS PC version added a keyboard mapping is user long-awaited things, a lot of people pretending Remix OS PC version of the original intention is to play the game, because they can not stand the card slow performance and poor compatibility simulator.
Last week, Remix OS PC version beta version added a keyboard mapping function to obtain beta users, no longer afraid of playing the game is not compatible.
Yes, today's main event is the keyboard mapping update was added, and now only for "vanity" and "human resource" adaptation keyboard mapping, follow-up will add more and more optimized game adaptation.
Upgrade:
You can check the OTA update system update
Download the full amount of the package
Baidu network disk || Click here to visit
the extraction code: gbku
360 cloud disk || Click to Visit
extraction code: 938d
Detailed update log:
new function:
Added "Apply recommendation", it recommended more suitable Remix OS applications
New image output, support output HDMI, DP and VGA interfaces, etc.
New settings - restore factory settings function
Add a button to switch your phone browser / computer mode functions
Added latest official recommended wallpaper
Latest update Remix OS boot animation
New low battery alerts
Optimize video playback, video playback support more formats
New gaming keyboard mapping support, recommend games to "vanity" and "human resource" can be installed in the application of Recommendation
Bug fix:
Enhance the stability of the system, the use of traditional mechanical hard disk, the system will be more fluent
Improve application compatibility, support for more applications running on the x86 platform, such as: Youku / Taobao / JX / Implosion / Yahoo Mail
Increased portion laptop touchpad right support
Improve Wi-Fi instability, adding support for more wireless network card, including Realtek / Broadcom / MediaTek
Optimization Nvidia graphics adapter problem
Optimization of temperature control notebook, laptop or tablet according to the temperature control system to prevent system crashes
When optimizing hard disk partition read, repair hard disk partition to mount, resulting in system issues Caton
Repair in some graphics cards cause the taskbar can display problems
Progress is inseparable from the system for your feedback, in order to better optimize Remix OS PC version, please stop for a moment, fill in the following three questionnaire to help us do a better Remix OS PC.
Remix OS PC version of the keyboard mapping gathering feedback || Click to Visit
Remix OS PC version of the perfect run hardware collection || Click to Visit
Applications Recommended || Click to Visit
Regnas said:
I thought the next update would be 3.0......
Click to expand...
Click to collapse
There're few bugs that stop Android-x86 6.0 from daily use. For example,Google play services always crash on Intel Gen8+ GPUs,which is not fixed yet.
But the devs at Jide are actively contributing to Android-x86 6.0 and you'll be able to see the results in near future. For instance,the issue of Time being reset in Windows is fixed
in the latest commit, Check the marshmallow-x86 branch at https://github.com/android-x86-mirror
Hmm...seems like a solid release. I will wait for the official announcement and update though. If it fixes my nvidia/wifi/sound issues I might actually start using this
Regnas said:
I thought the next update would be 3.0......
Click to expand...
Click to collapse
I think there is no remix os 3.0 for PC(x86) :crying: :crying: :crying: :crying:
I downloaded and installed it. My impression :
1 Locked DOWN, no more root command line
2 No Play Store option
3 Does include keymapping
4 Stock file manager can no longer read the partition on which Remix OS is installed
5 Maybe a little more quick because of changes to disk partition access
This may be because it is currently for Chinese users, hopefully there will be more flexibility with the release
EDIT 2016/07/01: After solving problems of getting into root command line, was able to deactivate jide app policy and then went on to install nova launcher, etc. Then using help from @HypoTurtle I was able to do systemless root. Everything now operating well. I will continue testing this 2.0.401 over the next few days for stability.
Summary:
1 No longer locked down
2 Play Store is activated
3 keymapping confirmed
4 Solid Explorer can read all disk partitions by using Stickmount
5 So far seems quicker than 2.0.205
Sent from my on Z00A using XDA Labs
Latest version is dated 29 June 2016..
For root , you need to replace the su file at system/xbin.
For play store option you need to got to setting , click on experimental ,on the alt+f1 option . You can active play store option .
Sent from my GT-N7105 using XDA-Developers mobile app
have anyone a working link/mirror to the new beta?
scanja500 said:
have anyone a working link/mirror to the new beta?
Click to expand...
Click to collapse
I have already posted this in two different threads, but here is a faster mirror, if anyone wishes to download.
https://mega.nz/#!9lkTWDiI!as99QTFGw2UYkFkHQWBVCX-pKpxkT7McLs27t-wfVHM
pengkoh1 said:
Latest version is dated 29 June 2016..
For root , you need to replace the su file at system/xbin.
For play store option you need to got to setting , click on experimental ,on the alt+f1 option . You can active play store option .
Click to expand...
Click to collapse
Thanks for explaining the experimental settings.
Was able to activate the Play Store
Pardon the noob question: where do I get the si file to replace the stock one?
Sent from my on Z00A using XDA Labs
lollyjay said:
Thanks for explaining the experimental settings.
Was able to activate the Play Store
Pardon the noob question: where do I get the si file to replace the stock one?
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
I used the remixroot.zip from here. I choose to install remix os in read write mode thus I can replaced the su file at system/xbin directly.
You have to follow the method describe in that thread if you install remix os in read only mode
Sent from my GT-N7105 using XDA-Developers mobile app
pengkoh1 said:
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
I used the remixroot.zip from here. I choose to install remix os in read write mode thus I can replaced the su file at system/xbin directly.
You have to follow the method describe in that thread if you install remix os in read only mode
Click to expand...
Click to collapse
Thanks. I installed Remix on a Windows computer so I cannot use Ubuntu method. Also I used the Remix installation tool so everything is stock install. Guess I will have to wait for a systemless root. @HypoTurtle are you onto this yet? (lol)
lollyjay said:
Thanks. I installed Remix on a Windows computer so I cannot use Ubuntu method. Also I used the Remix installation tool so everything is stock install. Guess I will have to wait for a systemless root. @HypoTurtle are you onto this yet? (lol)
Click to expand...
Click to collapse
If someone can post the ramdisk I'll compare to the previous version but regardless the current systemless root su/ramdisk.img should work fine; unless it's drastically different.
HypoTurtle said:
If someone can post the ramdisk I'll compare to the previous version but regardless the current systemless root su/ramdisk.img should work fine; unless it's drastically different.
Click to expand...
Click to collapse
I thought so too. But when I substitute the ramdisk.img I get to the RemixOS splashscreen and never boots further
lollyjay said:
I thought so too. But when I substitute the ramdisk.img I get to the RemixOS splashscreen and never boots further
Click to expand...
Click to collapse
In that case attach the ramdisk.img to a post here and I'll take a look.
edit. @lollyjay on your edit above -- you shouldn't need stickmount... check if the partitions are mounted to /mnt/media_rw/hdd*
1.
Black shark2(only)
H0 : Download this firmware mp3
H0_EEA : Download this firmware mp3
rename "update.zip" then put it "ota" Directory in your phone(if you don't have this directory, make it)
if you find step bs2 pro downgrade, see this link
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Won't this break the sensors?
batuken said:
Won't this break the sensors?
Click to expand...
Click to collapse
which sensor?
ripiad said:
which sensor?
Click to expand...
Click to collapse
Proximity and accelorometer sensors. I've just tried it and it didn't break them. Thanks for this.
ripiad said:
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
I'm not sure if this is going to flash probably this way on BS 2 Pro, as this contain extracted partitions and there is a flash script 'flash_all.bat' which I made to flash those partitions.
So 'flash_all.bat' should be executed to flash this.
Click to expand...
Click to collapse
Thanks for this thread this will make it easier for people to understand.
ripiad said:
1.
Black shark2
H0 : Download this firmware mp3
H0_EEA : Download this firmware mp6
then up it "ota" Directory in your phone(if you don't have this directory, make it)
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
then up it "ota" Directory in your phone(if you don't have this directory, make it)
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Click to expand...
Click to collapse
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
spikywits said:
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
Click to expand...
Click to collapse
There are may bugs in joyui11.
Navigation buttom array can reverse in fullscreen display which located settings. (select mirror button)
Lock the background app is possible. view recent app(press home button or slide bottom up) and long press app what you want to lock.
Then, you can see lock icon
ripiad said:
There are may bugs in joyui11.
Navigation buttom array can reverse in fullscreen display which located settings. (select mirror button)
Lock the background app is possible. view recent app(press home button or slide bottom up) and long press app what you want to lock.
Then, you can see lock icon
Click to expand...
Click to collapse
Sorry. I forgot to mention - I need to do this for stock android 9 on BS2. Once I downgrade from 10 to 9.
The older joy ui navigation menu sucks. It offers only gesture navigation and no option to lock apps. There is no 3 button navigation like other android platforms.
spikywits said:
Sorry. I forgot to mention - I need to do this for stock android 9 on BS2. Once I downgrade from 10 to 9.
The older joy ui navigation menu sucks. It offers only gesture navigation and no option to lock apps. There is no 3 button navigation like other android platforms.
Click to expand...
Click to collapse
how about using this? using adb.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
" "<- you can change this order
caution : when you reboot your phone, it go back previous
ripiad said:
how about using this? using adb.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
" "<- you can change this order
caution : when you reboot your phone, it go back previous
Click to expand...
Click to collapse
Thanks for the trick. I think there must be a way to persist this setting.
If I remember correctly, there are apps on store to change dpi on non rooted phone, which runs some adb commands to change the dpi value and make it to persist across reboot.
or using fluid navigation gestures app
https://play.google.com/store/apps/details?id=com.fb.fluid&hl=en
2. Then dial this from your phone
Code: *#*#1027#*#*
Click to expand...
Click to collapse
This code is not working on my device skw-h0. Any help would be appreciated.
spikywits said:
This code is not working on my device skw-h0. Any help would be appreciated.
Click to expand...
Click to collapse
Did you use 3rd party dialer?
this method based on google dialer(require default dialer)
ripiad said:
Did you use 3rd party dialer?
this method based on google dialer(require basic dialer)
Click to expand...
Click to collapse
I use the stock dialer and it the default one, although I have truecaller installed along with.
Regardless, I managed to fix the issue.
I did the following:
Code:
adb reboot recovery
wipe/factory reset
with nothing installed, dialed *#*#1027#*#* and got the ota update app to popup.( I had the dpi set to lower than stock before reset, not sure that could be a reason for incompatibilities. )
Thanks, I will come back if I get into issues again with the downgrade.
spikywits said:
I use the stock dialer and it the default one, although I have truecaller installed along with.
Regardless, I managed to fix the issue.
I did the following:
Code:
adb reboot recovery
wipe/factory reset
with nothing installed, dialed *#*#1027#*#* and got the ota update app to popup.( I had the dpi set to lower than stock before reset, not sure that could be a reason for incompatibilities. )
Thanks, I will come back if I get into issues again with the downgrade.
Click to expand...
Click to collapse
I think truecaller make this issue.
additional dialer caused this situation
ripiad said:
I think truecaller make this issue.
additional dialer caused this situation
Click to expand...
Click to collapse
I don't think truecaller cause this.
I successfully downgraded from android 10 to 9. Installed truecaller and tested the dial code, it instantly popsup the update software.
Thanks for documenting the steps. Infact, I used the updated ota image from KM7 thread - SKYW2003090OS00MP6.
I will work on to root this device now and keep it on 9 forever. No more miui based Android 10
Update:
warning: flashing SKYW2003090OS00MP6 directly broke my sensors.
Had to flash the MP3 update.zip in the opening post to keep the sensors working. Thanks for the zip.
spikywits said:
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
Click to expand...
Click to collapse
This can be done by turning off 'Swipe up on Home button' gesture, in Settings > System > Gestures.
spikywits said:
I don't think truecaller cause this.
I successfully downgraded from android 10 to 9. Installed truecaller and tested the dial code, it instantly popsup the update software.
Thanks for documenting the steps. Infact, I used the updated ota image from KM7 thread - SKYW2003090OS00MP6.
I will work on to root this device now and keep it on 9 forever. No more miui based Android 10
Update:
warning: flashing SKYW2003090OS00MP6 directly broke my sensors.
Had to flash the MP3 update.zip in the opening post to keep the sensors working. Thanks for the zip.
Click to expand...
Click to collapse
KM7 thread - SKYW2003090OS00MP6. is not OS00 firmware. that's OS01 firmware. Because I'm sharing this files first.
Today. I could get SKYW2003090OS00MP6 factory firmware(Korea ver.) so I'll modify it.
ripiad said:
1.
Black shark2
H0 : Download this firmware mp6
H0_EEA : Download this firmware mp6
then up it "ota" Directory in your phone(if you don't have this directory, make it)
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
then up it "ota" Directory in your phone(if you don't have this directory, make it)
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Click to expand...
Click to collapse
normal work on the black shark 2 pro DLT-H0?
my version is DLTR2004231OS00MQ0
I click on local update and nothing happens and non-local update when I click appears on the following message.
the list of update packages update / package_list does not exist
Version for Marshmallow is available here: https://forum.xda-developers.com/t/...zation-for-old-touchwiz-mm-framework.3372401/
Version for Nougat is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-n-framework.3692391/
Version for Oreo is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-o-framework.3749479/
Version for Pie is available here: https://forum.xda-developers.com/t/...-14-customize-samsung-oneui-24-05-20.3908114/
Version for Q is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-2-0-30-12-20.4044757/
Version for R is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-3-x-14-03-21.4212051/
Firefds Kit [ S ]
Xposed module for Samsung S devices.
Known working devices:
Galaxy S20
Galaxy S20
Galaxy S10
Features
The module has the following features:
Fake system status to Official
Custom advanced power menu options:
Power off
Restart
Emergency mode
Recovery (with custom text)
Download
Data mode switch
Screenshot
Switch User (when multi user is enabled)
SystemUI restart
Flashlight
Screen Recorder (requires Samsung screen recorder app installed)
Disable restart confirmation
Enable performing power menu reboot / power off actions only after unlocking secure lock screen (stock behavior)
Disable display of power menu when secure lockscreen is locked
Change default behavior of reboot to reboot to recovery
Replace Reboot to Recovery icon with system default restart icon
Enable call recording and call recording settings
Replace add call button instead of call recording and adding record by menu option
Clock Size option
Enable Call ID and spam protection option
Enable Screen Record tile and Settings options
Enable screen record while in call
Enable additional advanced hotspot settings option
Hide VoLTE icon in status bar
Hide persistent USB connection notification
Hide persistent charging notification
Enable block phrases in messages app settings
Enable native blur on notification panel pull down
Enable multi user toggle
Set max user value selector
Show seconds in status bar clock toggle
Show AM/PM for seconds on clock toggle
Show clock date on right of clock toggle
Add date to status bar clock options
Enable fingerprint unlock on reboot toggle
Enable biometrics unlock on reboot toggle
Add network speed menu to show network speed in the status bar
Data icon symbol selection (4G, LTE, 4G+, 4.5G)
Show Data usage view in quick panel
Double tap for sleep
Hide NFC icon
Disable Bluetooth toggle popup
Disable sync toggle popup
Disable high level brightness popup
Hide carrier label
Carrier label size selection
Disable loud volume warning
Disable volume control sound
Disable low battery sound
Screen timeout settings
NFC behavior settings
Auto MTP
Disable camera temperature check
Enable camera shutter sound menu
Disable call number formatting
Disable SMS to MMS threshold
Force MMS connect
Bypass exchange security (currently not working)
Disable signature check
Disable secure flag
Attention
This version was tested by the community and not by me, as I don't have an Android 12 Samsung device.
THERE COULD BE BUGS/CRASHES/BOOTLOOPS, but it's pretty stable.
Please upload any xposed logs when you encounter any issue. I can't help you without the logs!
Installation
To install this module you need the following apps and modules installed on your device:
Magisk v24.0 and above - https://github.com/topjohnwu/Magisk/releases
Option 1 - Zygisk
LSPosed Magisk Zygisk Release module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Option 2 - Riru
LSPosed Magisk module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Riru Magisk module v25.0.0 and above - https://github.com/RikkaApps/Riru/releases
Download
Directly from LSPosed Manager or from Github : https://github.com/Xposed-Modules-Repo/sb.firefds.s.firefdskit/releases
Source Code
https://github.com/Firefds/FirefdsKit/tree/S
Known Issues
A lot has changed since Android 11. Since I don't have an Android 12 device all tests have been done with various testers. THERE MAY BE UNKNOWN ISSUES!!
Some features are removed on purpose. Since GravityBox has been working on Samsung Oreo devices without much issues, I only implemented features that need special Samsung coding.
Reporting Issues
When reporting an issue, please include Xposed logs and screenshots if any. Reporting should be done through Github - https://github.com/Firefds/FirefdsKit/issues
External Libraries
The project uses the following libraries:
https://github.com/rovo89/XposedBridge
https://github.com/rovo89/XposedMods/tree/master/XposedLibrary
Samsung framework libraries which are used for compile only
EdXposed Whitelisting
Users who want to use EdXposed's whitelist feature should whitelist the following apps:
Android System - android
Call - com.samsung.android.incallui
Call Settings - com.samsung.android.app.telephonyui
Camera - com.sec.android.app.camera
Contacts - com.samsung.android.contacts
Email - com.samsung.android.email.provider
Firefds Kit - sb.firefds.s.firefdskit
Messaging - com.samsung.android.messaging
MTP Application - com.samsung.android.MtpApplication
NFC - com.android.nfc
One UI Home - com.sec.android.app.launcher
Settings - com.android.settings
Smart Capture - com.samsung.android.app.smartcapture
Software Update - com.wssyncmldm
System UI - com.android.systemui
Credits
This module wouldn't have been here without the following people:
RikkaW - Creator of Riru Magisk module, which provides a way to inject codes into zygote process
@rovo89 - Creator of the original Xposed framework APIs
solohsu and MlgmXyysd - Creators of the EdXposed Magisk module and Installer that made all of this possible
@C3C076 - Creator of GravityBox Xposed modules, which I learnt a lot from
@wanam - Creator of the original XTouchWiz module, which this module is based on.
@topjohnwu - Creator of Magisk
@AbrahamGC - For the Extended Power Menu - Pie - Odex framework Smali guide
Big thank you to @m8980 and @ianmacd for testing countless versions and sending xposed logs
Telegram
Announcements and pre release versions - https://t.me/firefdskit
This is a moded version of Wanam's XTouchWiz:
https://github.com/wanam/XTouchWiz
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
okij said:
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
Click to expand...
Click to collapse
Thanks! This looks great! I'll add it to the next version
firefds said:
Thanks! This looks great! I'll add it to the next version
Click to expand...
Click to collapse
Thanks! I'm glad you like it and look forward to the next version.
IIRC Firefds Kit 11 uses the same icons (I have been using it until I switched to Android 12 two months ago), so you might use the new icons there too.
Thanks.
All my devices now bootloop with NoClassDefFoundError: com.android.systemui.BasicRune
Any chance we could add those whitelists to LSposed "Recommended"? Exactly the most important call recording check is missing.
Btw if LSposed 1.7.2 is installed, Riru can be uninstalled? -> looks like Sui uses Riru, so no switching.
In the end, I could leave Firefds enabled if I don't change anything, luckily call recording is on by default.
Thanks for the update for Android 12. Everything working good on my A52s 5g. Hope that one day you can add the ability to adjust the height of the navigation bar. That was available in the gravitybox app but there is no upgrade for 12 yet and not sure there will be which is why I've asked here... appreciate your efforts though.
Is there an easy way to fix bootloop in case something went wrong?
donkeyman1234 said:
Is there an easy way to fix bootloop in case something went wrong?
Click to expand...
Click to collapse
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me delete it worked and I didn't have to disable lsposed modules or the magisk
Kuba1996 said:
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me it worked and I didn't have to disable lsposed modules or the magisk
Click to expand...
Click to collapse
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
donkeyman1234 said:
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
Click to expand...
Click to collapse
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root without custom recovery?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
You can look at last post here and try do something like that. Mabye try in recovery choose "update from adb" and try erase with adb command (your directory: riru-core). Or try use this but I dont think it will work
[Tool][Aroma] Magisk Manager Recovery Tool V2.5
Warning: It's not a Magisk module! Description This is a Magisk module management tool that can be used in Recovery mode. It's based on Aroma Installer. You can manage almost everything in Magisk with this tool. You can manage installed modules...
forum.xda-developers.com
Kuba1996 said:
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root witchout custom recovery?
Click to expand...
Click to collapse
I used magisk patched AP file to root. There is no twrp for s22u.
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Also You can flash in odin patched ap and rest of file but with HOME_CSC not CSC
Check this:
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Had the same issue with my s22u. I reflashed through odin. Gonna try and flash this module again with magisk bootloop protector. fingers crossed.
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Hello,
Thank you for A12 update.
So nice to have your magic on this version.
I would also love to see the ability to adjust navbar, and the possibility to move cursor with buttons in navbar like in GravityBox.
For me, Force MMS to connect isn't working on BeyondRom 4.1.
Is it working for others ?
I am using LSPosed zygist latest version and safety net 2.2.1
nishantgupta107 said:
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Click to expand...
Click to collapse
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
doggydog2 said:
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
Click to expand...
Click to collapse
Yes, some os settings did get reset. Not sure why. But now I'll wait for a stable release (I have reflashed it now 5-6 times)
Arobase40 said:
You can install Magisk Bootloop Protector module...
It will disable Magisk modules when bootloop occurs.
Click to expand...
Click to collapse
Thanks. I did install, but it did not work, the phone kept rebooting, reflash was my last resort.
Bootloop
S10 plus UI 4.1 A12
LSPosed-v1.8.0-6482-zygisk