Related
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
First, let's give credit where credit is due. @ZeNiXxX and @SKULSHADY are the developers of this ROM. Additional credit goes to @phhusson and @Dil3mm4 as well as:
LineageOS Team (https://www.lineageos.org)
AICP (https://www.aicp-rom.com)
MSM-Xtended Team (https://forum.xda-developers.com/one...0-pre-t3693585)
Crdroid (https://crdroid.net)
Omnirom (https://omnirom.org)
And all the other Developers, Testers, Donators and Users.
The source code which can be reviewed and continued too can be located here https://github.com/Havoc-OS and https://github.com/Havoc-Devices You can request features https://goo.gl/forms/b8rY79XtUZnd5ji42 Announcement are made here https://t.me/Havoc_OS and additional support can be requested here https://t.me/havocofficial. Finally, the official Havoc-OS page can be located here https://sourceforge.net/projects/havoc-os/files The original official thread is actually located here and was originally posted by @EnesSastim and an updated thread can be found here originally posted by @mountaser halak I, myself, @MotoX4 did full testing in verifying the support of MotoX4 having tested on several XT1900-1 (both Andriod One, Amazon Moto Retail, and * Project FI).
However, the purpose of this thread is only to bring awareness that MotoX4 users (such as yourself) do have another ROM to choose from and to include full instructions on how to install this on your MotoX4 device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Not working:
Tethering
- You tell me
FEATURES:
Code:
[SIZE="4"][B][U][SIZE="5"]General:[/SIZE][/U][/B]
System-wide Rounded UI
Full OMS support
System-wide burn-in protection
Spectrum support
Compiled using SDCLANG
Razer Phone lock/unlock sounds
OTA support
Signature spoofing
Micro-G support
[SIZE="5"][B][U]Included Apps:[/U][/B][/SIZE]
AdAway
Google Calculator
Google Markup
Lean Launcher
[SIZE="5"][B][U]Settings:[/U][/B][/SIZE]
[B][U]Battery:[/U][/B]
Battery performance profiles
Sensor block per-package
Wakelock blocker
Alarm blocker
Optimal charge level alert
[B][U]Display:[/U][/B]
Live display (Day/Night/Outside)
Colour profiles (sRGB, DCI-P3)
Font manager
Ambient display
Always on display
Expanded desktop
[B][U][SIZE="5"]Havoc Settings:[/SIZE][/U][/B]
[B][U]Status Bar:[/U][/B]
Quick pulldown
Smart pulldown
Tap to sleep
Brightness control
Battery icon styles
Bluetooth battery status
Battery bar
Battery saver color
Clock & date options
Statusbar logo
No sim network hide
Disable no sim icon
Volte icon
Network icon customization
Net activity
Custom carrier label
System icons
[B][U]Panels:[/U][/B]
Power menu tweaks
Volume dialog tweaks
[B][U]Quick Settings:[/U][/B]
Brightness slider customization
QS panel footer customization
QS layout editor
Custom header images
[B][U]Notifications:[/U][/B]
Disable fc notifications
Force expanded notifications
Disable immersive mode messages
Kill app button in notification
Screen-on notifications
Toast icon
Toast animation
Toast icon color
Toast text color
Heads up toggle
Heads up timeout
Heads up blacklist
Heads up stoplist
Snooze timer
Statusbar ticker
Ticker animation
In-Call vibration options
Less annoying in-call notifications
[B][U]Recents:[/U][/B]
Stock recents customization
Clear all button customization
Memory bar
Recent styles
Hide apps from recents
Icon pack
Immersive recents
Recents layout (Stock/Grid/Android Go)
OmniSwitch
Slim recents
[B][U]Interface:[/U][/B]
Berry styles (Light/Dark/Black/Auto)
Blur personalization
Dashboard suggestions
Dashboard conditions
Screen stabilization
[B][U]Lockscreen:[/U][/B]
Charging info
Hide statusbar
Lockscreen elements visibility
Notification count
Lockscreen colors
Clock and date options
Lockscreen alpha
Double tap to sleep
Wake and unlock
Ambient display music ticker
Ambient display bottom view (Weather/Battery/None)
Music cover art
Music visualizer
Disable power menu
Disable qs panel
Fingerprint vibration
FP unlock on boot
Face auto unlock
Custom bottom shortcuts
[B][U]Navigation:[/U][/B]
Navigation mode(Stock/Smartbar/Fling)
Dynamic navbar color
Pulse
[B][U]Buttons:[/U][/B]
Swap back and recents
Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer)
Accidental touch
Power menu customization
Long press power button torch
Disable buttons
Button backlight customization
Hardware keys customization
Swap volume buttons with rotation
Volume keys for media volume
Playback control
[B][U]Gestures:[/U][/B]
Three finger screenshot
Pie control
App circle bar
Gesture anywhere
Screen-on gestures
Touchscreen gestures
[B][U]Animations:[/U][/B]
System Animations
Android P animations
Disable animations
QS tile animations
Listview animations
Custom Bootanimation
Screen off animation
[B][U]System:[/U][/B]
SELinux mode Toggle
Smart Pixels
Suspend actions
System app remover
Allow untrusted overlays toggle (for Substratum Support)
CPU info overlay
[B][U]IME Settings:[/U][/B]
Selector notification
Auto keyboard rotation
Disable fullscreen keyboard
[B][U]Weather:[/U][/B]
Weather service settings
Statusbar weather
Lockscreen weather
[B][U]Miscellaneous:[/U][/B]
Screenshot editor
Wake on plug
Pocket detection
Camera shutter sound
Disable safe headset volume
Launch music App on headset Connection
Scrolling cache
Events[/SIZE]
How to install Havoc-OS on Moto X4
!! Please read before proceeding !!
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
!! You will be wiping everything because regardless if you are coming from stock or a different ROM as this ROM works best with a full wipe !!
Note: If upgrading this ROM a full wipe is not necessary. See upgrade instructions below.
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), select "advanced wipe" to wipe your device (select all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
If coming from stock:
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Continue:
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest Amr64 A/B ROM located here: https://sourceforge.net/projects/havoc-os/files/arm64-ab/ - NOTE: You want the ROM that comes without Gapps. You can install Gapps after (see instructions below).
Extract the zip (XZ file) onto your computer. -- I suggest the free and open source program 7zip https://www.7-zip.org/
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img /sdcard/
In TWRP select Install *
Select Install image
Locate your .IMG file and flash it to "SYSTEM"
* TWRP troubleshooting:
A small group of individuals has reported that TWRP will not correctly install IMG files directly. If you're one of those few people a manual install may work for you.
First wipe your phone again
Reboot back to bootloader. - Stay at bootloader
As an administrator on windows or as root on Linux run this command
Code:
fastboot -u flash system Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
Credit to @*.jpg for this solution.
NOTE: Do NOT yet install Gapps. See instructions below.
After a successful install, REBOOT your phone.
Congratulations, you're done!
If adding Gapps: -- Read me
Your phone will work perfectly fine without Gapps. But if you do want to install Apps and use Google products and services; I recommend the minimal Gapps install known as Pico. You can learn about the many different Gapps flavors by visiting the Open Gapps Wiki found here https://github.com/opengapps/opengapps/wiki/Package-Comparison
Let your phone boot the ROM for the 1st time. - !! IMPORTANT !! You want to fully boot your phone and let the ROM load for the 1st time before installing Gapps.
After your phone as successfully booted up and loaded the ROM, reboot back into recovery
Download the latest Gapps - https://opengapps.org
Upload the zip to your phone
Install Gapps
Wipe cache/dalvik
Additionally, if you're one of those paranoid people who want to keep your distance away from Google (to each their own, but I love me some Google ) you do have the following alternatives.
https://apkpure.com/
https://en.uptodown.com/android
https://f-droid.org
Just remember that these are unofficial sources and you take the risk that can potentially come with them.
UPGRADING - How to upgrade this ROM.
Also known as a dirty upgrade, you do not need to wipe everything and start over. However, if this dirty upgrade fails a fresh install is recommended.
Download the latest ROM
Reboot into recovery
Install your new .img file
Wipe cache/dalvik
Reboot
If all has gone well you're done! If not, a full wipe and install are recommended.
* Project Fi
If you do not have Google Project Fi as your cellular provider, you can ignore this.
The Google Project Fi app will inform you that you cannot activate using this GSI/Rom. Assuming, you have already previously activated your phone before trying out new GSI/ROM's, you can technically, safely ignore this warning as you will still be able to send and receive calls, text, data, etc... and continue to use the Project Fi app to manage your account. However, if this is your first time activating or you simply wish to be sure you get the latest carrier and tower updates (recommended), this fix is for you.
First let's give credit where credit is due. @Sass86oh for originally coming up with this fix here and a personal thanks to @johnjingle for pointing this out to me here.
Google Project Fi Fix
You will need to make a minor and yet important edit to your system before installing the Project Fi app. If you have already installed the Project Fi app before making this edit, you should close the app, clear both the app's cache and clear the app's storage, then proceed to uninstall the Project Fi app.
Using your preferred root text editor navigate to /system/
Locate the file build.prop
Carefully make the following changing, listed below, to the file build.prop
!! Important !! Double check you have correctly made the correct changes.
Save your changes
REBOOT your phone
Go to: Setting > System > About
Verify that your device model is a Moto x4
Install Project Fi
Open Project FI and proceed with the activation
Congratulations, you're done!
!! IMPORTANT !! These values are CASE SENSITIVE which means if you type "Payton" rather than "payton" it will NOT work !! Be sure you double-check what you type before saving !!
Locate and edit to match. -- Do NOT rush (Do NOT be in a hurry). This is something you want to carefully take your time with.
Code:
ro.product.model=Moto x4
ro.product.brand=Motorola
ro.product.name=payton
ro.product.device=payton
ro.product.manufacturer=Motorola
ro.build.product=payton
ro.opa.eligible_device=true
Headphone jack fix found here. credit: @abrfilho
????
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
abrfilho said:
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
Click to expand...
Click to collapse
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
SchmilK said:
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
Click to expand...
Click to collapse
Yeah, when I was using phh's Pie AOSP I was able to use the wide lens, even on modded GCam, but here I'm not able. ?
I already installed Moto Camera here.
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
*.jpg said:
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
Click to expand...
Click to collapse
How can you do that? I think I can't just fastboot flash havoc.....img right?
I installed via TWRP, but I am stuck at the android loading screen. I will try to re-flash I guess.
khanhlinh said:
How can you do that? I think I can't just fastboot flash havoc.....img right?
Click to expand...
Click to collapse
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
Code:
fastboot -u flash system [*your GSI here*].img
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
Click to expand...
Click to collapse
You can flash Magisk without a problem.
khanhlinh said:
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
Click to expand...
Click to collapse
I am having the same issue, except I get to the android text sometimes. I have tried installing the rom with gapps and w/out.
Not sure what I am doing wrong I came from Lineage trebelized and I did wipe everything even internal storage. Should be simple.
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
Click to expand...
Click to collapse
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
I only managed to enter system with GApps version by disabling all networks (removing SIM and not connecting to wifi), but everytime prompted some login, I could configure without a problem using the normal version with GApps flashed.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Nice work bro... Please keep it live and update it time to time
johnjingle said:
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Click to expand...
Click to collapse
can you skip if you turn the phone off and on again?
xdacinq said:
can you skip if you turn the phone off and on again?
Click to expand...
Click to collapse
unfortunately no. at the same position i got the loop. But the Version without gapps worked.
Well, I'm puzzled why some of you are having so many issues. I had 3 MotoX4's to play with and all of them worked without issue. Granted, all 3 are XT1900-1 devices and I wouldn't imagine a big different between XT1900-1 through 7. Did this with the original Amazon Moto Retail (the one which says Moto and not Andriod One), plus the Andriod One I got from Motorola and finally the Project Fi phone too (also an Andriod One edition), but none of them had the issues some of you are reporting. -- Which is why I felt confident sharing this in this forum.
I will add that I always used the ROM without Gapps included (and later installed Gapps after adding the ROM). Gapps tends to update often and I wanted to start fresh with the latest edition, so I installed the Rom without Gapps, confirmed that all was working, and then rebooted back into recovery and installed Gapps (as instructed in post 1).
For the few of you reporting issues... Perhaps start from scratch (as if coming from stock) and see if that resolves things.
I included this in the instructions and someone who sent me a PM made it clear where they were making mistakes. -- DO NOT install Gapps right away. Load the ROM 1st (let your phone boot up the ROM as if you're done and then reboot and install Gapps). I made this clear in my instructions and I think some folks are ignoring that little bit (those of you getting the "checking info" message).
I don't have this phone so this is untested by me but it is working on my Pixel 3 XL and @w0rdie got it to work on his Pixel 3.
This is in place until TWRP is ready. You need root and of course you need to be attached to your PC. On first installation of systemui base, a pop-up asking to give ADB shell root permission will show. Please do so.
The purpose of this installer is to generate for you a custom module that you can flash in Magisk Manager. It will have all the mods that you have selected from the installer menu.
Custom clocks (date, etc) and internet speed indicators do not change colors due to light-dark background colors like the statusbar icons do.
The developer of Active edge gave me permission to use his base so that people would not have to make a choice between his and my mods. All credit for this goes to him. You must delete the active edge sense module and use one of my active edge modules. If it doesn't say active edge then it isn't active edge sense compatible. If there is an issue with edge sense after flashing, do not contact edge sense op with issues. He does not troubleshoot modified versions of his mod (and neither do I).
I'm also including my Pixel Launcher mod. Also a ADB Installer. You can change app drawer background-text color (separately for light mode and dark mode), remove weather from Launcher. Change the number of hot seat icons on home page (and size) as well as change the number of columns in the app drawer.
ADB Installer Instructions-Root is required
1. Flash one of the SystemUI Bases First. They provide the necessary smali files and public ID's for everything to work.
2. FLASH ALL THE MODS YOU WANT. ONCE YOU DONE WITH EVERYTHING, FLASH THE "COMPLETE INSTALLATION" Option. This will create a Magisk Manager flashable zip in a folder on your sdcard called ozop. Flash that to install your selection of mods.
Root required
Instructions.
1. Unzip ADB Mods Installer Files.zip on your PC
2. Run TulsadiverModsInstaller.bat (Give ADB Root Permissions)
3. ADB debugging Enabled
4. Flash one of the SystemUI Bases First. They provide the necessary smali files and public ID's for everything to work
5. Go through the other options selecting what all mods you want. It is generally best to start at the top and work your way down.
6. Once finished with selections, run "Complete Installation" at the bottom. This will generate your mymagisk.zip module in a folder called "ozop" on your sdcard.
List of MODS Available
Clock Format and Position Mods
Internet Traffic Speed Single Indicator (changes from upload-download) otherwise signals are over/under
Choose Traffic Speed Indicator Up-Down Icon Colors (default is white)
Navbar Height Options
Navbar Swap
Remove NavBar
3 Minit Battery
One percent custom battery Mods-Several to choose from
One percent custom battery Text-only-Several to choose from
Colored Statusbar-Navbar Icons
Choose number of QS columns 3-7
Colored Statusbar Icons
Remove Carrier Text Options
Smaller LTE Icon
Custom Battery Sizes in case custom batteries are too large or too small
Android 11
ADB Installer uploaded 6-18-21
ADB Mod Installer Files11Pixel3.zip | by Tulsadiver for Pixel
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
-------------------------------------------------
If I helped, hit the Thanks Button!
Feeling generous, send me a beer!
--------------------------------------------------
---------------------------
Android 10
ADB Installer uploaded 6-4-20
https://www.androidfilehost.com/?fid=4349826312261825743
--------------------------------------------------------------------------------------
Pixel Launcher Mod
Start by picking a base. Bases come with, or without, a search bar and Hotseat heights The larger number of rows you pick, the lower your hotseat drops on your home screen. If your hotseat comes out too low, try again with a higher base.
Remove Search Bar
App Drawer background color (Light and Dark Mode)
App Drawer Text Color or remove (Light and Dark Mode)
Home screen App Text Color
Smart-screen Text color
App Icon Sizes 45-50-56 dip (56 is stock)
Columns (5-6-7)
Rows (5 through 11)
Android 11
ADB Pixel Launcher Installer uploaded 6-18-21
NexusLauncherReleaseADBPixel4XL.zip | by Tulsadiver for Pixel
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Would it be possible to make the notification icons for AOD colored?
arby80 said:
Would it be possible to make the notification icons for AOD colored?
Click to expand...
Click to collapse
I'd have to check on that. My lockscreen tint remover removes the black lockscreen tint and let's your lockscreen aod wallpaper show although not full color.
Noticing some color bugs with the Stock bases any no color mods applied. Volume profile switch icon, settings icon from QS (bottom right), etc..
How can I help resolve?
w0rdie said:
Noticing some color bugs with the Stock bases any no color mods applied. Volume profile switch icon, settings icon from QS (bottom right), etc..
How can I help resolve?
Click to expand...
Click to collapse
Don't use stock like. Stock like is very limited as to what you can flash.
What should I use if I only want the right clock and d/u by wifi..?
Stock colors, nav, battery, etc.
w0rdie said:
What should I use if I only want the right clock and d/u by wifi..?
Stock colors, nav, battery, etc.
Click to expand...
Click to collapse
What is d/u?
Oh, internet, just flash SystemUI base stock like, right clock, internet of choice. You don't even have to flash a framework base.
Single internet by WiFi also has up and down arrows. Just an FYI.
Tulsadiver said:
What is d/u?
Oh, internet, just flash SystemUI base stock like, right clock, internet of choice. You don't even have to flash a framework base.
Single internet by WiFi also has up and down arrows. Just an FYI.
Click to expand...
Click to collapse
Yeah that is what I did and ended up with the bugs I mentioned. (Labels/Buttons color issue).
Screen: https://i.imgur.com/isAt9nR.png
w0rdie said:
Yeah that is what I did and ended up with the bugs I mentioned. (Labels/Buttons color issue).
Screen: https://i.imgur.com/isAt9nR.png
Click to expand...
Click to collapse
I installed the Pixel 3 stock framework onto my Pixel 3 XL then flashed the very things I mentioned from the Pixel 3 ADB installer and got none of those things. Have you installed other mods such as edge sense?
Nothing else except the smaller LTE icon.
How do you install colored navbar icons or nexus navbar icons? I do not see the option listed in the prompt.
arby80 said:
How do you install colored navbar icons or nexus navbar icons? I do not see the option listed in the prompt.
Click to expand...
Click to collapse
You can't. I copied and pasted from Pixel 2 post. I'll change that.
@Tulsadiver Possible that it was the LTE icon mods that created the color bugs? I failed to mention that I did that too.
w0rdie said:
@Tulsadiver Possible that it was the LTE icon mods that created the color bugs? I failed to mention that I did that too.
Click to expand...
Click to collapse
No, I can't see how it could. You might try flashing system images and trying again.
Tulsadiver said:
No, I can't see how it could. You might try flashing system images and trying again.
Click to expand...
Click to collapse
Do I have to fastboot the system.img to revert to stock?
w0rdie said:
Do I have to fastboot the system.img to revert to stock?
Click to expand...
Click to collapse
That would be Best.
Tulsadiver said:
That would be Best.
Click to expand...
Click to collapse
Got it sorted. Narrowed it down to selecting option #1 from SystemUI menu rather than option #4.
Also - Others may not need to but I found that the script hangs if I don't use a second terminal to restart adb after a reboot.
My steps:
Using Windows 10 Powershell:
Open P.S. Window, ran adb shell | su
Open second P.S. window, ran TulsaDiverMods bat file
Selected SUI Base option [ 4 ] (not option [ 1 ])
Open P.S. Window, ran adb shell | su again (After reboot)
Selected Right Clock
Selected Internet Speed by WIFI
Selected Smaller LTE icon
Selected Complete Installation
It's perfect, no odd colors, etc.
w0rdie said:
Got it sorted. Narrowed it down to selecting option #1 from SystemUI menu rather than option #4.
Also - Others may not need to but I found that the script hangs if I don't use a second terminal to restart adb after a reboot.
My steps:
Using Windows 10 Powershell:
Open P.S. Window, ran adb shell | su
Open second P.S. window, ran TulsaDiverMods bat file
Selected SUI Base option [ 4 ] (not option [ 1 ])
Open P.S. Window, ran adb shell | su again (After reboot)
Selected Right Clock
Selected Internet Speed by WIFI
Selected Smaller LTE icon
Selected Complete Installation
It's perfect, no odd colors, etc.
Click to expand...
Click to collapse
So you want to select option 4 then for it to work as option 1 gives you issues? Also, this only works on the white status bar, eh?
Slomies said:
So you want to select option 4 then for it to work as option 1 gives you issues? Also, this only works on the white status bar, eh?
Click to expand...
Click to collapse
Depends on what you want. He wanted minimal mods and flashed the wrong SystemUI base for that. If you want something different, flash the first option and flash a framework base other than stock like.
Not sure what you mean by white status bar?
Tulsadiver said:
Depends on what you want. He wanted minimal mods and flashed the wrong SystemUI base for that. If you want something different, flash the first option and flash a framework base other than stock like.
Not sure what you mean by white status bar?
Click to expand...
Click to collapse
I have to mess with it then and see which option works best for me. All I want is center clock and a battery mod. You listed in the OP that the black status isn't working yet. I assumed that was the status bar.
Sent from my Pixel 3 using Tapatalk
GravityBox - all-in-one tweak box - Xposed module for devices running Android 11
Version 11.0.5 [R]
Version for JellyBean is available in this thread: https://forum.xda-developers.com/showthread.php?t=2316070
Version for KitKat is available in this thread: https://forum.xda-developers.com/showthread.php?t=2554049
Version for Lollipop is available in this thread: https://forum.xda-developers.com/showthread.php?t=3037566
Version for Marshmallow is available in this thread: https://forum.xda-developers.com/showthread.php?t=3251148
Version for Nougat is available in this thread: https://forum.xda-developers.com/showthread.php?t=3653953
Version for Oreo is available in this thread: https://forum.xda-developers.com/showthread.php?t=3739929
Version for Pie is available in this thread: http://forum.xda-developers.com/showthread.php?t=3908768
Version for Q is available in this thread: http://forum.xda-developers.com/showthread.php?t=3974497
READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
Introduction
The app utilizes Riru-EdXposed Magisk module which uses original Xposed Framework API created by rovo89.
!!!!!! WARNING !!!!!!
This module utilizes EdXposed Framework which is still in early development stage and may contain bugs or might not be fully compatible with the system of your Android device. I take no responsibility for any issues arising from using GravityBox with EdXposed and strongly recommend creating a full backup of your device before activating the module.
Requirements
- Magisk v21 or later
- Riru v23 or later (Magisk module)
- EdXposed Manager (Application)
- Avoid using Resource hooking support if possible (Can be disabled in EdXposed Manager settings)
Installation
This procedure assumes you have working Magisk installation.
1) Install Riru module in Magisk Manager
2) Install and run EdXposed Manager app and download Riru-EdXposed module v5.1.3.x or later (currently Alpha/Canary)
3) Install downloaded Riru-EdXposed module in Magisk Manager
5) Reboot and open EdXposed Manager app to check if EdXposed works and is active
6) Install GravityBox and enable it in EdXposed Manager
7) Reboot and profit
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Feature highlight
--- Lockscreen tweaks
--- QuickSettings tile management with additional tiles
--- Statusbar tweaks
--- Navigation bar tweaks
--- Pie controls
--- Power tweaks
--- Display tweaks
--- Phone tweaks
--- Media tweaks
--- Hardware/navigation key actions
--- GravityBox Actions - interface for 3rd party apps
--- Notification control (per-app notification LED/sounds/vibrations)
--- Fingerprint launcher
--- Advanced tuning of Framework and System UI parameters
... and many more
Compatibility
GB's main concept is to make most of the preference changes to be done on the fly without need to reboot a device to achieve custom-ROM like experience.
This means it is not possible to "completely deactivate" particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can't find elsewhere.
This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
If you experience weird issues after installing GB, even if you didn't activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM.
It is very similar to a situation when you installed ROM built from source for Nexus to some Xperia device - it won't work.
GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source, and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good.
GB being a complex module, it shouldn't be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there's no way you can deterministically say which one's going to win. They can even lose both.
So in summary:
- this module is designed to run on vanilla or close-to-vanilla Android 11 (AOSP)
- officially supports devices/systems it was developed and tested on
- Samsung, HTC, MIUI, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
- DO NOT USE WITH CUSTOM ROMS MODULE WAS NOT EXPLICITLY DESIGNED FOR
- I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
- I will not provide any support for devices violating these compatibility rules
GravityBox [R] has been designed for and tested on
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Reporting bugs
If possible, please use Github issue reporting interface for reporting bugs.
If you experience problems with certain feature, provide the full-detailed info that can help me
to reproduce the bug and attach logs that can be exported from EdXposed Manager app.
Real-time logging can be performed by using ADB: adb logcat -s EdXposed-Bridge
In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
Please, don't attach big logs. Only the portion where error is clearly seen.
Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
Remember, this app was developed and tested on one particular device so it is not guaranteed that it will work flawlessly on yours.
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Preferred way is to use GitHub interface to fork your own copy of GravityBox, make changes and then send pull request against original repository.
Anoter way is to simply download this file: https://github.com/GravityBox/GravityBox/raw/r/GravityBox/src/main/res/values/strings.xml
Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.
Source code
GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/r
If you're a dev and have some ideas for additional features, feel free to fork it, work on it and send the pull requests.
Copyright notice
https://github.com/GravityBox/GravityBox/blob/r/NOTICE
Support development
Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are more than welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!
Info about premium features and PayPal transaction ID verification system
1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
As of v2.9.5, there are three premium features:
- Backup/restore of GB settings.
- Ultimate notification control
- Advanced Tuning
2) If you contributed to the project by providing translations, code fragments, or by any other way
you can apply for a free transaction ID by contacting me via PM.
3) Be aware that there's a system that can identify potential transaction ID
abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
In case you own more devices, you can use one transaction ID on up to 10 of them.
4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
upon verifying your ID as verification system accepts requests only from official releases of GB.
If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
a special hash for your build.
If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
it is necessary to ask for new hash everytime your new custom version is released for public use.
These rules are based on mutual trust so please, do not violate them.
Credits
- RikkaW for creating and maintainng Riru Magisk module
- solohsu & MlgmXyysd for creating and maintaining EdExposed Magisk module
- @frank93 for donating Pixel 3a for development
- @bgcngm for his code contributions to the project
- @MohammadAG for Xperia specific contributions to the project
- @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
- @peptonib for starting me up with this project
- @simmac for app icon
- @romracer for Motorola specific code contributions
- @firefds for Samsung specific code contributions
- CyanogenMod project
- ParanoidAndroid project
- Slim, RootBox, AOKP, OmniROM projects
- Sergey Margaritov for ColorPickerPreference
- ArthurHub for Image cropping library
- All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, Fatih Firinci, ...)
- and finally, all those who keep the project alive by supporting me via donations (you know who you are)
Changelog
https://github.com/GravityBox/GravityBox/blob/r/CHANGELOG.txt
Changelog 11.0.5 - 08/08/2021
- Lockscreen: added option to blur media artwork on lockscreen (thanks to robbins)
- Navbar: allow cursor control keys in gestural navbar
- Dialer: adjusted for compatibility with the latest Google Dialer
- Properly identify OnePlus 8T as device running OxygenOS ROM (thanks to F-i-f)
--- should improve compatibility significantly
Developed and tested on:
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Current issues
- Display: Expanded Desktop - immersive modes not working
- Key actions: Home double-tap not working
- Lockscreen: Changed custom carrier text won't appear immediately
- Custom Battery indicator: stock battery may appear for a while after the reboot
- ... + potentially others mainly device/system variation specific
Removed features
- GPS and SlimKat tiles - location modes (battery saving/high accuracy/device) no longer exist in Android 11
- Audio Recording tile - background recording of audio not possible in Android 11
Download
https://github.com/GravityBox/GravityBox/releases/tag/v11.0.5_r
Settings
It is possible to restore settings that were backed up in GravityBox [Q]
Simply transfer "GravityBox" folder from internal storage of one device to internal storage of another device.
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Credits
@frank93 for donating Pixel 3a for developemnt
Commit history
Commit history for transition from 11.0.4 to 11.0.5
@C3C076
Mate, you did it. Congratulations.
Can't wait to try it out.
Really appreciate your efforts in bringing this to us 11ers.
Cheers
2021 is looking good! Thank you so much. Working flawlessly on my pixel 3a
@C3C076
THIS is the first gift I've received of the new year. Thank you, sir!!!
Now, that's pretty awesome!
And the January update from Google should drop soon as well.
Thanks a lot @C3C076!
Got my Github notification this morning about the [R] pre-release! Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems. Everything working perfectly fine! All I had to do was first disable GravityBox [R] in EdXposed Manager, and disabled Kirisakura AK3 (kernel) module helper in Magisk Manager. Upgraded to Android 11 with no issues at all, and everything system and root-wise seems to work perfectly fine. My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
Though I'm gonna play it safe and OTA each month, instead of factory image (sans "-w" flag) jumping. Gonna work my way up to the current firmware, then test out GravityBox [R] - thanks so much @C3C076! The fact that so many people like me have held off on upgrading to the latest Android version just based on your work should speak volumes! I'll report back once I'm able to actually play around with GB[R] some. The baby's starting to wake... :O
edit: my son rolled over, coo'ed, and faceplanted back to sleep <3
- Also should note, I was on Kirisakura 5.2.6 kernel before. Now on 6.6.0, all is well!
- Also wanted to note, SafetyNet was passing (with my current configuration) on 09-2020 build with no further modifications necessary. I just finished updating up to 12-2020, and SafetyNet is still passing . Activating GravityBox module now, and will further report back!
edit 2: Seems verrrry stable so far! The only thing I found that didn't work properly (or rather, worked 80% correctly) was for an option that I don't even normally use, and accidentally toggled, haha. Under QuickSettings management -> Tiles per header, each option works fine, but when selecting 8, it still only shows 7.
Other than that, at least as far as the options that I personally use, everything seems fine! I didn't get a chance to test out every function affected by my set of GB options in such a short time, of course, but I will certainly report if there are any issues. And of course I won't list every single option I ticked off, but attached is my backup file / preferences of my current config for anyone who may be curious. Again, keep in mind that compared to the vast functions GB offers in totality, I only use what I use so of course I can't account for the entirety of GB. But from what I've tested so far, it seems damn stable and this has made my transition to Android 11 pretty much seamless!
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
i5lee8bit said:
Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems.
[...]
My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
[...]
Activating GravityBox module now, and will further report back!
Click to expand...
Click to collapse
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Ghisy said:
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Click to expand...
Click to collapse
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
i5lee8bit said:
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
Click to expand...
Click to collapse
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
i5lee8bit said:
see my edit above =)
Click to expand...
Click to collapse
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
If I can share my experience. I applied standard system update procedure from settings being on Pie (had it on your pixel to bring update for GB for Pie). This went without uninstalling magisk etc. I simple went incrementally from Pie through Q up to R and then several security update. Only after I was in the latest update I grabbed boot.img from corresponding system image, patched it using magisk and then flashed using fastboot. All apps and settings were preserved from Pie.
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
frank93 said:
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
Click to expand...
Click to collapse
Yeah, note that I never flashed full rom image. I went using standard system update from settings. In the end it was only patched boot.img I flashed.
okay, apparently not even a "real" firmware update (using the original stock boot image) works for me. loops back to bootloader 2-3 seconds after the google-logo. so i guess there’s something else wrong with my device/system.
i’ve "updated" back to the latest/last android 10 for now (there the firmware upgrade/downgrade works!?), and i’ll scratch my head another time i think. thanks for your input though!
i5lee8bit said:
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
Click to expand...
Click to collapse
Thanks, I appreciate it! You took one for the team and shared interesting info too! *(air) high five*
C3C076 said:
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
Click to expand...
Click to collapse
I use App List mode, but not White List mode, as I use the Pass SafetyNet option (so basically on Blacklist mode). Because I also have GPay working and all (I've linked to that thread before, it's the one I linked with my list of active modules). Hahaha, I didn't even realize you put in the 2nd post about it not working - weird! Definitely working for me though, using these current configurations.
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
Since I'm sure others may find it useful, I'll post it here. Also, @C3C076 may find it useful to follow this concept, assuming things are similar for Pixel 3a (I've been a long time HTC user, up til U12+ and only then switched to Pixel phones, 4 for wife and 4 XL for me to be exact).
My firmware update procedure is basically predicated on restoring the stock boot and dtbo (dtbo in case custom kernel flashed) images for your current build, which restores the stock firmware (and therefore recovery) and "unroots" / stock-ifies the phone without removing any of your Magisk or EdXposed configs, which allows you to simply boot into recovery and apply (sideload) OTA zip from stock recovery. Before booting back into system after OTA flash, reboot back into bootloader and flash the new build's Magisk-patched boot image, and when you boot up into system, voila, seamless, intuitive, and relatively safe update to new firmware version. Worst case scenario, if you bootloop you just flash the stock boot image (or even better, a modified Magisk Core Only boot image) and fix whatever is causing the problem.
Here is a link to my guide for September 2020 build, which was the first Android 11 build. There's a bunch of additional notes due to the major update at the time, though some of the info is a bit outdated. I assumed everyone at the time was on a very specific versions of firmware, Magisk, EdXposed, and even modules, etc. But if you read, especially the 2nd post, you can certainly understand how it all works and how we could apply the process from any firmware version. Here's the thread: https://forum.xda-developers.com/t/...0-009-coral-magisk-stock-boot-images.4160787/
- I recommend giving the procedure a read, as you should be able to understand the intuition behind the process I use.
As we're already (assuming) on latest Magisk, Magisk Manager, EdXposed, Riru, etc. etc, we don't need to worry as much about compatibility of our installed modules before OTA'ing. So basically, I condensed down what needs to be disabled, in my case, to the old GravityBox module (obviously), and the old Kirisakura (my kernel on Q) kernel helper Magisk module. You would also want to disable any modules, Magisk and EdXposed, that may not be compatible with [R] yet.
So here was my update procedure, from here on, coming from August 2020 build already on Magisk 21.2 and up to date EdXposed / Riru / etc. modules - SPECIFICALLY FOR PIXEL 4 XL "CORAL"
(OPEN THE "SPOILER" TO VIEW!):
Spoiler: Pixel 4 XL (and by extension and intuition, hopefully other Pixel series) keep-root / updating guide-procedures
NOTE: The files I provide are specifically only for Pixel 4 XL!! You will need to obtain the correct files for your own device to follow this procedure, but the same idea should be able to be applied!
First, I downloaded the boot and dtbo file(s) for Aug. 2020 thru Dec. 2020 builds. Here's a link to my AFH uploads for these files: P4XL Boot / DTBO files
Then, I patched each month's boot image with Magisk 21.2, and put them to the side.
There's only stock dtbo.img for 08-2020 because dtbo will remain stock throughout the updating procedure, fyi.
Actually, hell, for Pixel 4 XL "Coral" users, to make your life extremely easy, I've uploaded all the files you'll need to follow this here!! - LINK HERE
And OTA files from Google servers: LINK#2 HERE
Disabled GravityBox [Q] module in EdXposed Manager / Uninstall GravityBox [Q]
(Don't bother installing GravityBox [R] yet)
Disabled Kirisakura AK3 Kernel Helper module in Magisk Manager
(you'll also want to disable any modules that potentially may not work with [R])
-- Reboot once to finalize disabling the modules --
(Don't boot back into system until this section is done, to ensure all root, settings, mods, etc. are retained - this is basically the 2nd post of the September guide I linked earlier)
- Reboot into Bootloader mode -
fastboot flash boot 08-boot.img
fastboot flash dtbo 08-dtbo.img
(these steps revert recovery to stock)
- Reboot into Recovery mode-
(when No Command / Android icon shows up, hold power button and tap volume up to get to recovery menu)
Choose option: Apply update from ADB
adb sideload (09-2020 OTA zip).zip
after OTA zip flash completes, REBOOT BACK TO BOOTLOADER
fastboot flash boot 09-patched.img
- NOW REBOOT INTO SYSTEM! -
When your phone boots back into Android (11), you will be rooted, with all mods and settings retained. And if you passed SafetyNet before with the right combination of mods and settings, it should still pass now. While you can, I wouldn't yet bother installing GravityBox [R] quite yet. Let's first continue to incrementally upgrade until we're at 12-2020 (or 01-2021 depending on when you're reading this). Basically, just make sure the Android System Update notification (sorry, I don't remember exactly the notification label, but you'll know when you see it) indicates the update completed before proceding.
Now we just repeat my OTA update procedure again, except no need to flash stock dtbo images, as we're not doing anything (like flashing custom kernel) in this short amount of time that modifies the dtbo partition.
Reboot into bootloader mode
fastboot flash boot 09-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (10-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 10-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 10-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (11-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 11-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 11-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (12-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 12-patched.img
Boot to system
EDIT: Google released January 2021 firmware update, literally minutes after (or maybe while??) I was posting this! Here is my January 2021 easy update guide for Pixel 4 XL: https://forum.xda-developers.com/t/...5-003-coral-magisk-stock-boot-images.4213263/
Allow time for the system update notification to indicate update was completed.
Install GravityBox [R], activate module, reboot one more time, have fun!!
Also install custom kernel or whatever else you might need to do as well.
To be honest, I kinda rushed this post, so I'll re-read it later and make sure I didn't make any little mistakes. But hopefully if you read my guides threads and stuff (like, actually read it), the entire concept should be very clear and intuitive to you! Assuming other Pixel phones (at least AB Pixel devices) have similar partitioning schemes, this should be very useful knowledge to have, as it makes updating to new firmware versions incredibly easy and low risk. Good luck, I hope this huge post helps some people / makes a better day for someone! =)
EDIT: @frank93, seeing your linked post, I see you have a Pixel 4a. Unfortunately you obviously can't use the exact files I provided / linked, but you should still be able to follow the same procedure. Just grab the OTA's, plus the full factory images, pull the necessary boot and dtbo files from the factory images, and Magisk patch the boot images for each month, and name / organize all the files and put them aside on your computer. You should still be able to follow my procedure, but with your files. I hope it works for you with no problems if you decide to try it!
Has anyone tried one plus 8t?
...aaaand Pixel January 2021 update just dropped
Awesome! 2021 is looking good! Donation sent! Keep up the awesome work bro! Working flawlessly on my Pixel 3xl
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working (READ CAREFULLY)
TWRP doesn't work, at least the one by vache, THEREFORE INSTALL MAGISK ON ANDROID 11! Thanks (and sorry) to @Zainullahk1234 for signaling this problem on the guide
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATION (install magisk while on android 11)Ok let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
I SUGGEST INSTALLING MAGISK WHILE YOU ARE ON ANDROID 11 WITH TWRP!
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this "guide" comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first!
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALL
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
The aux output didn't work the first time, we have to tweak some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX (this needs a better solution)PREMISE: This works only if you don't need Bluetooth headsets because we are going to disable it I think (I'm not an expert)
Open Developer Options in settings.
Find Disable Bluetooth Hardware Offload and enable it
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Force headset switch (Huawei defaul...
Enable Use alternate way to detect headsets
That's it, reboot for safety measure.
If you know how to do this in a better way please help us below! I don't need bluetooth that much but it's better to have it than not.
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol.
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
bluetooth headset can fixed by going in develpers setting and turning on disable bluetooth a2dp hardware offload and that looks like this:
wesleyvanneck12345678 said:
bluetooth headset can fixed by going in develpers setting and turning on disable bluetooth a2dp hardware offload
Click to expand...
Click to collapse
Ye but that way aux/jack stops working for me
Tommy0000 said:
Ye but that way aux/jack stops working for me
Click to expand...
Click to collapse
heh i got both enbled and it works for me
wesleyvanneck12345678 said:
heh i got both enbled and it works for me
Click to expand...
Click to collapse
Ok! I'll try!
Wich one have you enabled?
disable Bluetooth offload in dev options
force switch in phh patches
alternate switch in phh patches
Maybe it's a coded not supported by my headset
Tommy0000 said:
Ye but that way aux/jack stops working for me
Click to expand...
Click to collapse
foudn the fix go to phh treble settings > misc features and enable use alternate way to detect headsets
Can you tell me, just to be sure what is enabled and what not? @wesleyvanneck12345678
Tommy0000 said:
Ok! I'll try!
Wich one have you enabled?
disable Bluetooth offload in dev options
force switch in phh patches
alternate switch in phh patches
Maybe it's a coded not supported by my headset
Click to expand...
Click to collapse
Tommy0000 said:
Can you tell me, just to be sure what is enabled and what not? @wesleyvanneck12345678
Click to expand...
Click to collapse
1 and 3 and also dont forget to enable disable Bluetooth offload in phh treble settings > misc features
wesleyvanneck12345678 said:
1 and 3 and also dont forget to enable disable Bluetooth offload in phh treble settings > misc features
Click to expand...
Click to collapse
Thanks, i'm going to update the guide!
It works for me too!
Tommy0000 said:
Thanks, i'm going to update the guide!
It works for me too!
Click to expand...
Click to collapse
btw you sayed bluetooth audio doesnt work it does work with same settings
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same settings
Click to expand...
Click to collapse
I hadn't enable offload fix in phh's patches menu, maybe it was that, maybe I forgot to turn on something else when I tried
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same set
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same settings
Click to expand...
Click to collapse
Click to expand...
Click to collapse
you have to enable this to for bluetooth audio phh treble settings > misc and then features force-disable A2DP offload
so that in develpers settings and treble settings has to be anbled for bluetooth audio for aux force switch in phh patches
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
View attachment 5464431
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
Holy crap thank you sooo much.. I love this pixel gsi 12 ROM running on moto g stylus 5g 2021..
Bluetooth and 2g only for calls and text were my only bugs...
Now Bluetooth works flawslesy with this guide...
Any fix for volte..
I tried to flash the Qualcomm zip fix but twrp error"arcititure unknown"'
Anyone???
Awesome ROM guys... keep up the great work .
jhjhjhjhjhjh said:
Holy crap thank you sooo much.. I love this pixel gsi 12 ROM running on moto g stylus 5g 2021..
Bluetooth and 2g only for calls and text were my only bugs...
Now Bluetooth works flawslesy with this guide...
Any fix for volte..
I tried to flash the Qualcomm zip fix but twrp error"arcititure unknown"'
Anyone???
Awesome ROM guys... keep up the great work .
Click to expand...
Click to collapse
With Bluetooth you mean Bluetooth headsets? You should try with patches for audio that i included in the guide, idk much about it tho :/
Tommy0000 said:
With Bluetooth you mean Bluetooth headsets? You should try with patches for audio that i included in the guide, idk much about it tho :/
Click to expand...
Click to collapse
Yes my Bluetooth before I found this guide my audio was choppy and distorted...now it's just like my stock ROM...I'm so happy now...thanks..
Viper and Dolby both working on with Bluetooth as well...loving it!!!!
Again I just need a volte fix...I have to turn off volte and the data turns to "E" then calls and text work fine...but on LTE/5g no calls or MMS.. I use a free text app for now as a work around...
jhjhjhjhjhjh said:
Yes my Bluetooth before I found this guide my audio was choppy and distorted...now it's just like my stock ROM...I'm so happy now...thanks..
Viper and Dolby both working on with Bluetooth as well...loving it!!!!
Again I just need a volte fix...I have to turn off volte and the data turns to "E" then calls and text work fine...but on LTE/5g no calls or MMS.. I use a free text app for now as a work around...
Click to expand...
Click to collapse
There is a volte fix in patches too i think, also to me the preferred data connection was 3g maybe try to change it
3g setting puts my phone in "E' Wich is 2g speeds basically..I get calls and MMS but slow data...I have a 5 g phone that supposed to have MMS and calls over LTE/NR....
Tommy0000 said:
There is a volte fix in patches too i think, also to me the preferred data connection was 3g maybe try to change it
Click to expand...
Click to collapse
jhjhjhjhjhjh said:
3g setting puts my phone in "E' Wich is 2g speeds basically..I get calls and MMS but slow data...I have a 5 g phone that supposed to have MMS and calls over LTE/NR....
Click to expand...
Click to collapse
Yes this doesn't work do some roms do give you 5g do its android 11
t
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
View attachment 5464431
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
when i installed it it didnt come with magisk?
im on arm64 ab
Zainullahk1234 said:
t
when i installed it it didnt come with magisk?
im on arm64 ab
Click to expand...
Click to collapse
Ohhh very weird, it happened to me once, try reinstalling system without wiping user data and using another date build, maybe they forgot to put it in :/