stayboogy [ROM] AOSP 12L (12.1.0_r3, SPA2 5G) for Pixel 5 [redfin] - Google Pixel 5 ROMs, Kernels, Recoveries, & Other

stayboogy AOSP 12L (12.1.0_r3, SPA2 5G) Redfin
sources:​
base repo: https://android.googlesource.com/platform/manifest/+/refs/heads/android-12.1.0_r3/default.xml
my work: https://github.com/stayboogy/stayboogy_Redfin
this rom: https://github.com/stayboogy/stayboogy_Redfin/tree/main/aosp/12.1.0.r3
kernel: https://android.googlesource.com/device/google/redbull-kernel/+/refs/tags/android-12.1.0_r3
Built on the stability of stock without all the Google junk.
____________________________________________________________________________
FEATURES:​
*5G Radio Activated [without any Google Apps or Services Installed]
*stayboogy Pixel Recovery--work in progress based on aosp recovery
--modded to be able to install updates even after they fail signature verification
--modded to be able to use adb shell
--modded to work on this device specifically--work in progress
*Rootable
--https://github.com/stayboogy/stayboogy_Redfin/blob/main/aosp/how_to_root
*GApps Magisk Module Capable
--https://github.com/stayboogy/stayboogy_Redfin/blob/main/aosp/Magisk_GApps
*Visual Voicemail directly in the Dialer app
*Call Recording Working and Activated
--listen to recording from Call Details
*Messaging
--export and import message threads to storage, swipe right to delete
*Gesture Navigation by default
--change in settings
*Round Icons
*Monet Color Extraction implementation from kdrag0n [protonAOSP]
*System Accent Color changes based on Wallpaper Color Extraction [always on]
--want a different color, change your wallpaper--literally many colors even cyan like lineage, just play around
*Adaptive Icons Backgrounds change based on Wallpaper Color Extraction [always on]
--if doesn't automatically change with wallpaper, just toggle themed icons in wallpaper and style settings to correct
*Adaptive In-App Themes change based on Wallpaper Color Extraction [always on]
*App Themes Change based on Light / Dark System Theme Settings [always on]
*Custom Bootanimation
*Custom Wallpapers
*Custom Workspace Grid Sizes
*Lawnicons' Themed Icons already embedded in the default Launcher3 [Lawnchair not needed]
*Retro Audio Files from Cyanogenmod from LineageOS
*ExactCalculator from LineageOS
--in app theme changes based on Wallpaper Color Extraction
*Recorder from LineageOS
*Play All Media Files straight from Files App
--no separate music / video player needed
*No QuickSearchBar on HomeScreen
*No Browser
*No Calendar
*De-Googled
THIS ROM IS MEANT TO BE GOOGLE-FREE AND STILL BE CUSTOMIZABLE AND CAPABLE
{
"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"
}
Download:
stayboogy_Pixel5-12L-AOSP-5G_v2.0b
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
MD5:
md5sum.stayboogy_Pixel5-12L-AOSP-5G_v2.0b.zip
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
CHEATCODES:​
I. GApps
If you want to use apps like YouTube and Voice to Text or any other app that requires GSF/GMS from Google, then use the Magisk Module method, which will allow you FULL GOOGLE ACCOUNT ACCESS.
stayboogy_Redfin/Magisk_GApps at main · stayboogy/stayboogy_Redfin
Redfin. Contribute to stayboogy/stayboogy_Redfin development by creating an account on GitHub.
github.com
If you don't want to follow the directions above, you can just install the Magisk GApps Core Module and use any app that requires GSF/GMS without logging in. This will allow things like Voice-to-Text to work perfectly without a Google Account and this is how I use Voice-to-Text and GBoard
II. Backup & Restore Apps+Data between ROM Releases
I have provided a free app in the app repository "oandbackup" that you can backup and restore all apps and their data, user and system both. I have tested with user apps and it works fine. This will allow you to backup and restore your actual data without TWRP which is unlikely to ever be working for this ROM. Also, I am not going to implementing a backup option on the Pixel Recovery I am making either.
Just use to the app to batch backup your user apps and their data, copyt the files to your comptuer, and then copy them back to your phone after you install a new release and pick up right back where you left off.
III. Contacts & Text Message Backup and Restore
Contacts can be exported and imported directly from the app.
Messages can be exported and restored with adb:
//backup
adb root
adb pull /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db-journal
adb pull /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db
//restore
adb root
adb shell rm /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db-journal
adb shell rm /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db
adb reboot
adb root
adb push mmssms.db-journal /data_mirror/data_ce/null/0/com.android.providers.telephony/databases
adb push mmssms.db /data_mirror/data_ce/null/0/com.android.providers.telephony/databases
adb reboot
IV. App Repository
I have provided a few common apps for your convenience so that you can get to downloading and installing whatever you need should you not have your required apps backed up already before installing this ROM. I have provided Aurora Store, Magisk, and oandbackup.
App Repository
stayboogy_Redfin/aosp/app_repository at main · stayboogy/stayboogy_Redfin
Redfin. Contribute to stayboogy/stayboogy_Redfin development by creating an account on GitHub.
github.com
HOW TO ROOT:
stayboogy_Redfin/aosp/how_to_root at main · stayboogy/stayboogy_Redfin
Redfin. Contribute to stayboogy/stayboogy_Redfin development by creating an account on GitHub.
github.com

links are live--no gapps version only at the moment
gapps version coming as soon as I can get uploaded

new build coming [1.8] with lawnicons now in the quickstep launcher for themed icons without lawnchair, but also now if you have lawnchair without having to install lawnicons and it's not installed now either, and it is so freaking beautiful...
also, now Dialer, Messages, and Contacts use Contact Colors to reduce the monochrome nature of the theme while the action bars are still the same color as the accent color just like in the 1.7 build released in the OP

v1.8 live folks.
by far the best, most beautiful release from me yet for this device. themed icons are so freaking beautiful, even third party apps get themed...lots of them...

Does it support wireless power share?
Thanks!

badaas said:
Does it support wireless power share?
Thanks!
Click to expand...
Click to collapse
Couldn't tell you...don't have another pixel to test it out. If it's in the stock kernel it's here too

I've been using my own rom now exclusively and haven't had any issues.
Firefox nightly installs and works fine and works with autofill as well, without any google stuff.
This rom is mainly for those not needing/wanting gapps. It's definitely legit.

OP Updated.
GApps now supported through the linked Magisk Module in the OP (should you require them--tested and working fine--This Does NOT allow you to sign into a Google Account or the Play Store or Download from the Play Store BUT THIS DOES Let you use any app requiring GSF/GMS without logging in, youtube, voicetyping, etc all working when downloaded from the Aurora Store but you cannot sign into your account you can try but it won't happen, this is intentional)
Instructions on how to root added
Magisk App Download link added
Aurora Store App Download link added
Still the most power-user friendly, stable, de-googled, vanilla rom available for the Pixel 5

working on adding visual voicemail
adding swipe to delete to messaging
adding battery share service from lineage

v2.0 coming tonight with visual voicemail
build in process currently--all my builds are always built from a "m clean" so that you always get the most reliable, stable, stayboogy worthy builds

I'll have a new build up later today--visual voicemail is working, swipe right to delete messages has been enabled as an option in settings, debugging options have been enabled in messaging which allows you to dump and restore individual message threads straight from settings, and now the system accent colors for icons and app themes are more vibrant instead of dull looking like they were before.
very nice improvements

new link v2.0 live

I am working on creating a device specific recovery--stayboogy Pixel Recovery
so far, it is coming along nicely. my hopes are to get it to the point where people who really really want GApps can install them from recovery. They may not still work even then, but I'd like others to have the option. I'm doing lots of test right now on all of these things.
I can build GApps inline, but everyone will have to submit their android id to Google individually because I am not doing any work to make this rom GApps compatible.

I have added:
New link v2.0b with a new vendor_boot with the beginnings of the Pixel Recovery
Cheatcodes
--directions on how to backup and restore Contacts & Messages between ROM Releases
--directions on how to backup and restore Apps + AppData between ROM Releases
--App Repository including the app used to backup and restore apps+appdata

ROM can now use GApps fully with signing in, following the directions added to OP
so, now all your GApp needs can be fulfilled, making this the PERFECT ROM for the Pixel 5

stayboogy_Officially said:
stayboogy AOSP 12L (12.1.0_r3, SPA2 5G) Redfin
sources:​
base repo: https://android.googlesource.com/platform/manifest/+/refs/heads/android-12.1.0_r3/default.xml
my work: https://github.com/stayboogy/stayboogy_Redfin
this rom: https://github.com/stayboogy/stayboogy_Redfin/tree/main/aosp/12.1.0.r3
kernel: https://android.googlesource.com/device/google/redbull-kernel/+/refs/tags/android-12.1.0_r3
Built on the stability of stock without all the Google junk.
____________________________________________________________________________
FEATURES:​
*5G Radio Activated [without any Google Apps or Services Installed]
*stayboogy Pixel Recovery--work in progress based on aosp recovery
--modded to be able to install updates even after they fail signature verification
--modded to be able to use adb shell
--modded to work on this device specifically--work in progress
*Rootable
--https://github.com/stayboogy/stayboogy_Redfin/blob/main/aosp/how_to_root
*GApps Magisk Module Capable
--https://github.com/stayboogy/stayboogy_Redfin/blob/main/aosp/Magisk_GApps
*Visual Voicemail directly in the Dialer app
*Call Recording Working and Activated
--listen to recording from Call Details
*Messaging
--export and import message threads to storage, swipe right to delete
*Gesture Navigation by default
--change in settings
*Round Icons
*Monet Color Extraction implementation from kdrag0n [protonAOSP]
*System Accent Color changes based on Wallpaper Color Extraction [always on]
--want a different color, change your wallpaper--literally many colors even cyan like lineage, just play around
*Adaptive Icons Backgrounds change based on Wallpaper Color Extraction [always on]
--if doesn't automatically change with wallpaper, just toggle themed icons in wallpaper and style settings to correct
*Adaptive In-App Themes change based on Wallpaper Color Extraction [always on]
*App Themes Change based on Light / Dark System Theme Settings [always on]
*Custom Bootanimation
*Custom Wallpapers
*Custom Workspace Grid Sizes
*Lawnicons' Themed Icons already embedded in the default Launcher3 [Lawnchair not needed]
*Retro Audio Files from Cyanogenmod from LineageOS
*ExactCalculator from LineageOS
--in app theme changes based on Wallpaper Color Extraction
*Recorder from LineageOS
*Play All Media Files straight from Files App
--no separate music / video player needed
*No QuickSearchBar on HomeScreen
*No Browser
*No Calendar
*De-Googled
THIS ROM IS MEANT TO BE GOOGLE-FREE AND STILL BE CUSTOMIZABLE AND CAPABLE
View attachment 5645461View attachment 5645463View attachment 5645467View attachment 5645471View attachment 5645473View attachment 5645477View attachment 5645479View attachment 5645481View attachment 5645483View attachment 5645485View attachment 5645487View attachment 5645489View attachment 5645491View attachment 5645493View attachment 5645495View attachment 5645497View attachment 5645507View attachment 5645501View attachment 5645503View attachment 5645629
Download:
stayboogy_Pixel5-12L-AOSP-5G_v2.0b
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
MD5:
md5sum.stayboogy_Pixel5-12L-AOSP-5G_v2.0b.zip
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
CHEATCODES:​
I. GApps
If you want to use apps like YouTube and Voice to Text or any other app that requires GSF/GMS from Google, then use the Magisk Module method, which will allow you FULL GOOGLE ACCOUNT ACCESS.
stayboogy_Redfin/Magisk_GApps at main · stayboogy/stayboogy_Redfin
Redfin. Contribute to stayboogy/stayboogy_Redfin development by creating an account on GitHub.
github.com
If you don't want to follow the directions above, you can just install the Magisk GApps Core Module and use any app that requires GSF/GMS without logging in. This will allow things like Voice-to-Text to work perfectly without a Google Account and this is how I use Voice-to-Text and GBoard
II. Backup & Restore Apps+Data between ROM Releases
I have provided a free app in the app repository "oandbackup" that you can backup and restore all apps and their data, user and system both. I have tested with user apps and it works fine. This will allow you to backup and restore your actual data without TWRP which is unlikely to ever be working for this ROM. Also, I am not going to implementing a backup option on the Pixel Recovery I am making either.
Just use to the app to batch backup your user apps and their data, copyt the files to your comptuer, and then copy them back to your phone after you install a new release and pick up right back where you left off.
III. Contacts & Text Message Backup and Restore
Contacts can be exported and imported directly from the app.
Messages can be exported and restored with adb:
//backup
adb root
adb pull /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db-journal
adb pull /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db
//restore
adb root
adb shell rm /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db-journal
adb shell rm /data_mirror/data_ce/null/0/com.android.providers.telephony/databases/mmssms.db
adb reboot
adb root
adb push mmssms.db-journal /data_mirror/data_ce/null/0/com.android.providers.telephony/databases
adb push mmssms.db /data_mirror/data_ce/null/0/com.android.providers.telephony/databases
adb reboot
IV. App Repository
I have provided a few common apps for your convenience so that you can get to downloading and installing whatever you need should you not have your required apps backed up already before installing this ROM. I have provided Aurora Store, Magisk, and oandbackup.
App Repository
stayboogy_Redfin/aosp/app_repository at main · stayboogy/stayboogy_Redfin
Redfin. Contribute to stayboogy/stayboogy_Redfin development by creating an account on GitHub.
github.com
HOW TO ROOT:
stayboogy_Redfin/aosp/how_to_root at main · stayboogy/stayboogy_Redfin
Redfin. Contribute to stayboogy/stayboogy_Redfin development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
I am very interested in trying out this rom but one concern. If I'm on the latest 12.1.0 firmware which is SQ3A.220605.009.A1 can I flash and boot this rom or do I need to downgrade my firmware to the SP2A first?? Sorry if this is a dumb question I've just been out of the game for a while and dont wanna spend the whole day trying over and over so I figured I'd better ask lol. I'm sure it doesn't matter but I am running the official LOS 19.1 right now which I did flash myself so I'm not a complete noob I just wanna play it safe.
Thanks a lot!
DROIDROMMER

DroidRommer said:
I am very interested in trying out this rom but one concern. If I'm on the latest 12.1.0 firmware which is SQ3A.220605.009.A1 can I flash and boot this rom or do I need to downgrade my firmware to the SP2A first?? Sorry if this is a dumb question I've just been out of the game for a while and dont wanna spend the whole day trying over and over so I figured I'd better ask lol. I'm sure it doesn't matter but I am running the official LOS 19.1 right now which I did flash myself so I'm not a complete noob I just wanna play it safe.
Thanks a lot!
DROIDROMMER
Click to expand...
Click to collapse
As long as your bootloader is unlocked you can flash anything...no need to downgrade first.
Just download and install using the script in the zip file. Very easy just like installing the factory image. Being on lineage won't effect anything.
My ROMs install just like a factory image instead of an ota package. Mine are full flashes done on the bootloader & fastbootd.
Just unzip, reboot to bootloader, and run install.sh/install.bat depending on your platform

stayboogy_Officially said:
As long as your bootloader is unlocked you can flash anything...no need to downgrade first.
Just download and install using the script in the zip file. Very easy just like installing the ota. Being on lineage won't effect anything.
Click to expand...
Click to collapse
Awesome! Thanks a lot man. I'm gonna give it a try in just a bit.

hey is this still being updated @stayboogy_Officially ?

Related

Software Development [CLOSED] [ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V9a3 2018-04-22

========================================ACHTUNG===================
=================WARNING==========================================
=====================================================PELIGRO=======
AS WITH ANY UNSUPPORTED SYSTEM MODIFICATIONS, USING THIS MAY LEAD TO A BRICK
IF YOU DON'T KNOW WHAT YOU ARE DOING ( HAVEN'T BRICKED MY SYSTEM YET! ) PLEASE
BE AWARE THAT NO ONE ON THE INTERNET IS RESPONSIBLE FOR ANY DAMAGE TO YOUR
UNIT. ANY PROBLEMS WILL BE CONSIDERED ACTS OF WHATEVER GOD YOU BELIEVE IN.
======PELIGRO=======================================================
================================WARNING============================
===ACHTUNG=========================================================
For FYT SoM (5009/6011/6021/6022/6023) based JOYING / Intel SoFIA units ONLY!
Hello, here is a custom rom based on the SYU Stock Build [sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.bsp.20180110.181524 release-keys]
Your Head Unit MUST ALREADY BE ROOTED! You must be able to obtain Super User access within Android!
Due to Bluetooth, WiFi, and as well as nvram patches in the ROM and bootloader, you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM.
Why this ROM? Simple answer: It's makes your Head Unit faster than running the stock ROM's, has updated Google Apps, and has the bloat removed! It's pre-rooted also!
INSTALLATION INSTRUCTIONS:
Step 1: Unzip the contents to the root of your USB flash drive on your computer, then plug the flash drive into the Joying unit via USB.
Step 2. Use the Android helper application "custom" to install. Download from link below, either on the Head Unit itself, OR on PC and transfer using ADB. Once installed, open the program, and grant superuser privileges when prompted, you'll be presented with screen as here:
{
"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"
}
Step 3: Click INSTALL CUSTOM. Wait for output to say recovery successfully installed!
If you wish to preserve your /data, AKA dirty-flash, click on "Do not wipe data" at this point to prevent your data partition from being wiped.
ALL EXISTING DATA ON UNIT WILL BE ERASED. THIS IS A CLEAN INSTALLATION!
Step 4: click REBOOT TO INSTALL GTX ROM - Your Joying unit will reboot, and installation will automatically proceed through TWRP.
(NOTE! The ROM automatically re-installs stock recovery during installation, so if something goes wrong, you can always restore to the original JOYING firmware.)
Recovery options:
RESTORE STOCK - Restores the original stock recovery
INSTALL CUSTOM - Installs superdave's custom recovery (needed to install this ROM)
VERIFY RECOVERY - tells you which recovery you have installed
Rom Utilities:
(all options on this menu work only if you have custom recovery installed)
"Do Not Wipe Data" Switch - enable this to prevent your /data partition from being wiped when installing the ROM. (Your results may vary. Works for me!)
REBOOT TO TWRP - Reboots to TWRP home screen allowing you to do things
INSTALL GTX ROM- installs joying_gtx stock rom from installation media
Exit - exit custom
Code:
====Includes====
xposed v87 x86
open gapps x86 Nano Feb 2018
ViPER4ANDROID FX
precompiled dalvik cache (first boot 2 minutes)
enabled eth0 at boot at 192.168.65.100 for debugging
ADB enabled
SeSuperuser built-in
Included [custom] app to manage superdavex's custom recovery for easy installation and maintenance
RightCamera (front cam app) modified APK
AOSP android boot animation
Interactive cpu governor:
go_highspeed_load set at 70% CPU load
titanium backup
nova launcher
GVC CallHandler 4 Joying
Amaze File Manager
Xposed modules:
boot manager
gravitybox
no overlay warning
immsersive mode forcer
app settings
fake wifi
GPSSpeedFix
======Removed======
[I]Debug Services:[/I]
usbactive
sqldebug
pekallfmrserver
watchdog
ap_logfs
apk_logfs
log-watch
crashlogd
adbusbmuxd
adbec
bootwatcher
shcmd
fmd
[I]Removed Apps:
[/I]
BasicDreams
BluetoothMidiService
Exchange2
Galaxy4
HoloSpiralWallpaper
LiveWallpapers
LiveWallpapersPicker
NoiseField
OpenWnn
PhaseBeam
PrintSpooler
GooglePinyinIME
RKUpdateService
CaptivePortalLogin
WAPPushManager
[I]removed from /system-priv-app
[/I]ManagedProvisioning
CallLogBackup
OemTelephonyApp
DeviceTest
StressTest
WallpaperCropper
GoogleFeedback
ProxyHandler
CellBroadcastReceiver
[I]Removed FYT APPS[/I] ( these slow the system down considerably, even when not in use )
SYU-1-C9-Calculator-V1.0
Sofia-1-C9-TV-V1.0
JY-1-C9-Video-V1.0
JY-1-C9-TimeWeather-V1.0
SYU-1-FileManager-V1.0
SYU-1-C9-Update-V1.0
Sofia-1-C9-ExDvr-V1.0
SYU-1-C5009-DVR-V1.0
Sofia-1-C9-Gallery-V1.0
JY-1-C9-MUSIC-V1.0
ZBox
note, this is a test release intended for developer users only. no support other than this post is offered. A final version will follow soon once initial testing has been completed.
Download Links
Installer ( unzip, this will help you install the ROM on a STOCK, un-rooted Head Unit ) :
xxxxx Mod Edit
custom V4_9
xxxxxxx Mod Edit
source code
Firmware Download:
V9 ALPHA 3
xxxxxx Mod Edit
Reserved for TWRP instructions.
Q / A:
Q: Do I need to worry about what MCU version I have before I use your rom?
A: Maybe, GTX ROM doesn't touch the MCU, which shouldn't be re-flashed with each install anyway as it usually doesn't change. Whatever MCU version you have, this ROM will work for you, as long as you have an FYT based SoM unit. If you encounter errors, you might need to change the "ro.build.fytmanufacturer" property in /system/app/fyt.prop to match whatever your unit ORIGINALLY came with.
Q: I have a RK3066/RK3188/PX3/PX5 based head unit. Will this ROM work for me?
A: NO! This ROM ONLY works on FYT based head units. This means all Joying Intel units, as well as some from other brands.
Q: I like Live Wallpapers. How do I enable them?
A: Use the built in terminal. type su and hit enter. You now have root. then type in:
Code:
cp -R /system/vendor/oem/LiveWall* /system/app
hit enter again, then reboot!
Q: I don't want to use this ROM anymore, what do i do?
A: Use the helper application, custom, open the program, and click RESTORE STOCK. This will restore the STOCK RECOVERY. Go on Joying's website [link], download the firmware of your choice, and follow their instructions.
Q: Can I use google voice to make hands free calls?
A: You sure can. Use the "Voice Search" app to dial a number using your voice, once at the Google App screen, click on the hamburger menu, and then select GV CallHandler 4 Joying. Make sure your unit is set to a DPI of at least 161dpi or greater, and then clear data on the google app. After you reboot, you should be able to make calls.
Q: How do I view my front camera?
A: If you are using the analog RCA video input, on the back of the unit, you can use the RIGHT CAMERA app to view. Note, than unlike the AUX program, this one will NOT mute the system audio.
Q: How can I fix my GPS speed to calculate 1/kmh or 1/mph steps instead of the default 4 steps?
A: Go to XPOSED INSTALLER, and enable the GPSSpeedFix module. Reboot, and the steps will be fixed.
Q: How can I enable different DPI settings for each application?
A: Go to XPOSED INSTALLER, and enable the App Settings module. Exit the installer, and open the App Settings to make your adjustments. Reboot, and your changes will be visible.
Q: This ROM is fast, but I want more speed, what do I do?
A: Add a fan to your unit, preferably a FAN + Heatsink. Then download an app like SetCPU to lock your CPU to MAX speed. Be careful.
Q: How do I re-assign the hard keys on my unit? Joying says that DVD and EJECT don't work! Is this a lie?
A: Yes! There is a way to re-assign keys, and the DVD and EJECT keys do actually work, the software that comes with the unit is not very good. Check @surfer63's XSofiaTweaker thread for more info on how this works.
Q: I want to send and receive my text messages on my Joying unit...is this possible?
A: Sure! Use third party app like Pulse, or Pushbullet. Works like a charm. I personally use Pulse, it's got the look and feel of a stock SMS app.
Q: Installing the Joying Factory Rom takes like an hour...multiple reboots, then it starts over, then it reboots, then it optimizes apps, then it starts over, again. jeez. How long does your ROM take to install?
A: Installation is less than 4 minutes. First boot is timed at one minute 53 seconds, and there are no crashes or reboots. It just works.
Q: Xposed says there is an update available! Is it safe to update Xposed?
A: NO! Do NOT update Xposed, it will make your unit non-functional! Just say NO!
Q: Am I able to "upgrade" from an earlier version of the ROM to a newer without loosing my data and apps?
A: Yes, read the first post on what option to select in custom. Many others and I have tested, and it works for almost all people, still there is a chance that it could not work.
Q: I need to download the stock Joying firmware so I may use your ROM! Where do I get the latest updates?
A: See here: https://drive.google.com/open?id=1nF5Pgn95_WWGk8S2byb8rR5ko0ss5F_S
Q: is there a video where I can see you install the ROM?
A:
Issues:
-Unable to send text message via google voice app using Pulse SMS, error is "Message couldn't be sent" // If anyone has a fix for this, please let us know
-Google Assistant doesn't work, launching activity manually results in "The Google Assistant doesn't work on this device" / You can fix this by changing the resolution to at least 720. use the command wm size to change the screen resolution or another tool that can change DPI
Release History:
custom helper:
V4_1: Fixed installation issue from micro sd cards.
V4_2: Check OS build fingerprint, will deny install unless you are on 20171215 or later.
V4_3: Updated text on installation screen for easier reading, Updated build detection logic
V4_4: Fixed bug in build detection logic
V4_5: Added no_data_wipe, translations included.
V4_6: fixed reboot to twrp not extracting recovery ota.
V4_7: lbug fixed
V4_8: script improvements
V4_9: prepare for re-write, added performance mode
ROM:
V4: Replaced opengapps with nano version
V5: Updated to 01-10 AOSP Base, Added bluetooth build property from @surfer63, more optimizations.
V6: Added Navi APK, more optimizations, CANBUS firmware included, various stability fixes, ability to "dirty flash", mcud included to prevent bootloops during app optimization, works with 800x600 units now, fixed overlay bug, faster first boot, added ViPER4ANDROID, added USB audio policy modifications.
V7: Fixed LED issues and AMP Options. Updated GAPPS base to 20180226, might need to optimize apps on first boot if you are dirty flashing. Added fyt.prop to /system/app fix various issues.
V8: Changes in the way the installer handles re-installation of stock recovery for disaster recovery situations in which the installation fails and custom recovery remains installed, changed installation logic to to compensate for faulty installation media, twrp bug fixes, fixed twrp restart loop, clear FYT flags on twrp start.
V9 alpha 1:
updated recovery busybox to 1.27
fixed SYU file manager not found in CM Settings
fixed right camera not displaying
updated MCUd build to co-exist with sofia server
eliminate audio pops during rebooting
updated gtx_installer
updated dalvik cache
fixed recovery_maintenance.sh in system and recovery envrionments
recovery maintenance.sh is now functional from recovery console
updated clean_rom.sh
permissions overlay fixed
fixed script logic in install-recovery on 6021 units
include terminal app APK
added nano x86 editor
added network_up.sh to ensure debug network access and SU daemon is always run
v9_alpha_2:
fixed drm video black screen issue
added rom version information to fyt_build.prop
sofiaserver runs audio through all channels during call
v9_alpha_3:
xposed module to prevent xposed from updating framework causing bootloops
added remount command to path
added display calibration app to launcher
include both 5_25 and 9_20 versions of McuUpdateAll.bin in /system/mcu/ (copy the corresponding version to /system/mcu)
keep JET and other apps as user to ease upgrade
V3 Rom link not working?
Just finished upload, Try now.
gtxaspec said:
Just finished upload, Try now.
Click to expand...
Click to collapse
Yes, works fine. Sorry for clicking the links too early
I can't do anything with it now, but a link is so easily clicked.
my joying head units have an internal amp, can I use this ROM?
usa911g said:
my joying head units have an internal amp, can I use this ROM?
Click to expand...
Click to collapse
Yes, no problem at all. If there are bugs we will share them all. Nothing specific for amp or no-amp models.
surfer63 said:
Yes, no problem at all. If there are bugs we will share them all. Nothing specific for amp or no-amp models.
Click to expand...
Click to collapse
because the EQ app for amp or non-amp models is different, so I concern that
usa911g said:
because the EQ app for amp or non-amp models is different, so I concern that
Click to expand...
Click to collapse
Actually it is one and the same app with different screen-layouts and functionality depending on the hardware.
The digital amp software is included.
Reserved.
As soon as I have time I will try this rom
the russian hackers at 4pda are using the following build.prop mods, anyone care to chime in? if they actually do something, I will include them.
Code:
ro.rk.install_non_market_apps=true
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
persist.telephony.support.ipv4=1
persist.telephony.support.ipv6=1
persist.sys.purgeable_assets=1
ro.wifi.channels=14
media.stagefright.enable-http=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
I have no idea about the build props.
The custom V3 app did install the recovery image in one go. I do not know whether you improved something or the previous time was a glitch on my system when it gave that verification error.
I installed the V3 ROM. It works fine. It seems indeed faster than the original joying stock rom.
From what date are the GAPPS? The unit is trying to update all gapps. It is not really useful to have everything pre-odexed for a quick start (and it really is a quick start), when it immediately starts updating once you have finished the Google account setup.
(I myself also prefer the GAPPS micro package. I don't need and want google photos, youtube, google fit, etc. on my head unit.)
My JET apk is only partly working. At this moment I do not know why.
Replacing apps with mods (radio, BT, sofiaserver) works again now the apps are installed in /system/app
Copying the launcher.sh to /data does work. The launcher.sh works with the SofiaServer keymod as well as with the Xposed module sofiaservercustomkeymod (the one that uses the launcher.sh).
Installing a newer version ór installing one of the xposed modules currently doesn't work as it requires the package installer. The default package installer has been replaced by the googlepackageinstallers from the gapps. As such I can easily work around it by simply writing the apps to their folder in /system/apps. As soon as I upload my modules to the global xposed repository it is no problem anymore anyway as the Xposed installer can install it. I will still looking into why that one can install and my app not. I will also uninstall the google installer and replace it with the default package installer and see what happens.
And with regard to the customkeymod xposed module with settings screen: The settings screen itself works fine, but I still can't use the settings from my app. They stay empty.
Ok, if you think the microgapps is lighter I can cook that in.
gtxaspec said:
Ok, if you think the microgapps is lighter I can cook that in.
Click to expand...
Click to collapse
You might even consider nano or pico gapps and let users just install whatever else they need manually.
I'll do nano on v4 release which will be out tonight.
gtxaspec said:
I'll do nano on v4 release which will be out tonight.
Click to expand...
Click to collapse
Is Viper4Android working on this ROM?
Some time ago you said that you will investigate why is not working on the stock Joying but you never returned with an answer, can you please share your findings if you have any?
Thank you !
---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------
surfer63 said:
(I myself also prefer the GAPPS micro package. I don't need and want google photos, youtube, google fit, etc. on my head unit.)
Click to expand...
Click to collapse
I second this .... I also prefer things kept extremely simple !
haven't tested viper. I will install it tonight and test it tomorrow morning on my drive.

[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ & J6+ [j4primelte & j6primelte]

[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ & J6+ [j4primelte & j6primelte]
{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Fingerprint on J6+
Sim slots
Flashlight
Mobicore keystore
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Download the latest build.
Reboot to recovery
Flash the latest build.
Optional: Flash GApps for Google Services and Magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+/J6+ [j4primelte & j6primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-01-29
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-25
Last Updated 2020-01-29
Changelogs :
Stable version 1 - 29/01/2020 :
Now we are building vendor too. Goodbye OneUI vendor.
Happy news to J6+ users: my builds are now supporting j6primelte.
NFC is fixed on NFC variants.
Keystore is now fixed and got rid of aosp's software implementation. You don't need any hacks or tricks to make it work on GSIs.
SIM count detection added, single sim users won't have annoying second sim.
Previous build had dead flashlight sometimes. Fixed.
Removed Samsung's bloatwares.
RIL working delay after boot fixed.
And so much more that I did in past couple of months that I don't remember.
Public Beta 4 - 18/08/2019 :
MTP totally fixed.
Added FM Radio.
NFC should work now on FN users (Current device I have isn't NFC variant. I am not sure).
Public Beta 3 - 27/06/2019 :
Added USB and Bluetooth tethering.
Public Beta 2 - 26/06/2019 :
Lockscreen password fixed.
Audio on camcorder(video recording) fixed.
Autobrightness fixed.
Hotspot fixed.
MTP fixed.
Second SIM Slot fixed.
Public Beta 1 - 25/06/2019 :
First release.
Thanks to abhishek987 for thread template.
Screenshots on attachment.
Note(s) :
Send me logs if you've find any bug.
Reserved for just-in-case.
Please give me credits while building roms and sharing with my sources.
By hitting thanks button and following me on GitHub you can make me happy. Have fun!
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Andhika24kd said:
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Click to expand...
Click to collapse
Yes.
New update released. Enjoy.
ataberkozen said:
New update released. Enjoy.
Click to expand...
Click to collapse
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
rudi021 said:
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
Click to expand...
Click to collapse
Are you also building a ROM?
Geckyn said:
Are you also building a ROM?
Click to expand...
Click to collapse
yes.i build roms.i build also few gsi for j4+ just for test.but mostly for mtk devices.is my first samsung device.is my hobby. i have 55 years.
ataberkozen said:
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Flash RMM Bypass and forceencrypt disabler from TWRP thread.
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Optional: Flash magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ [j4primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-26
Last Updated 2019-06-25
Click to expand...
Click to collapse
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Necrosis Virus said:
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Click to expand...
Click to collapse
Some notes and bugs encountered by me on J415F:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Andhika24kd said:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Click to expand...
Click to collapse
1-) OpenGApps telegram group aware of this problem, wait for them.
2-) Prepaid doesn't show for me too, but others shows.
3-) I'll disable it later.
4-) Send logs from telegram.
5-) I forgot to add lineage livedisplay while creating tree. I'll add next update.
6-) SkiaGL problematic on sd425, 425 phones are using opengl. I had to choose between fixing lags and other ui problems or working screenshot. I choose first one.
7-) You said yourself, removing system apps causes bootloop.
I'll fix it later.
9-) IDK is it problem or not but i am pretty sure isn't bcz of me.
10-) Same 9.
11-) I didn't faced problem while sending mp3, but if u you can send logs i'll check.
12-) Not my problem.
13-) Not bcz of me.
14-) I didn't faced but it's app bug really not my problem.
15-) Not my problem 2.
16-) You said yourself install gboard.
17-) Accent colors is overlay based. Bug isn't from my side.
1 App feature missing or buggy. Idk java I cannot fix.
19-) It's not problem by me, even official devices same.
20-) I am aware of this problem. I need to find a way to change it to rssi.
21-) Isn't this point of DND ? I am busy don't send me any notifications ?
22-) Set ro.lcd.density to 280 with build.prop editor and report back.
Sorry I'm quiet busy nowadays (and I'm sure you are). I will upload the log (you mean logcat, right?) when I have time. Yeah, some of these bugs are actually features on AOSP/LineageOS, I'm just informing other users in case it's their first time switching from Samsung ROM to LineageOS or AOSP based ROM.
11) I didn't use the Bluetooth directly, Google Play Games used it to find a match with nearby player on the game "Bowmasters", will send logcat later.
16) Installing Gboard doesn't help, I already tried that 3-4 days ago.
19) Yes, I'm just informing the others in case they never tried LineageOS/AOSP before. However some unofficial LineageOS have that. Of course I'm not asking you to make/merge it, I don't care about themes.
22) Setting it to 280 doesn't help so far, but I think I need more time to see if it works or not.
Andhika24kd said:
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
Click to expand...
Click to collapse
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
breversa said:
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
Click to expand...
Click to collapse
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
ataberkozen said:
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Click to expand...
Click to collapse
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
breversa said:
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
Click to expand...
Click to collapse
MTP fails while copying from phone to pc.

[New][App] Choose between Bubble and ChatHead in Facebook Messenger (Android 11+) [No-Root]

[No-Root] - [Open Source] - [Safe for FB Account]
New -> [Included a Manager to patch apps on your phone]
A safe and clean way to select ChatHead or Bubble in Facebook Messenger.
Note: If your phone is rooted, you should follow the root method instead. Check this Thread.
Download:
- ChatHeadEnabler-v2.4.5.apk (422 KB)
Requirements:
- Uninstall all facebook apps (only for the first time): facebook, messenger, facebook lite, etc.
- First Install ChatHeadEnabler module.
- After that, Install a patched Messenger app from here.
- That's all.
[If you need any other facebook apps (facebook, facebook lite etc), install them from here too]
Get Patched Apps:
Now there are two ways you can get patched messenger app.
Safest and easiest way is to patch apps yourself with MRVPatch Manager (including any future updates as soon as facebook releases them), there's no need to use other peoples modified messenger. Another way is to download pre-patched apps from here (see below).
Download MRVPatch Manager: (to patch apps yourself)
- MRVPatchManager-v2.0.1.apk (7 MB)
Spoiler: Screenshots
{
"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"
}
[Watch video tutorial for MRVPatchManager]
[If you want to patch using pc tool instead, see pc instruction from below]
Download pre-patched apps: (last update: 10-Mar-2023)
- Messenger-v408.1.0.16.113.apk (64 MB)
- Facebook-v414.0.0.30.113.apk (78 MB)
- Facebook-lite-v354.0.0.8.108.apk (2.1 MB)
- Business-suite-v405.0.0.25.113.apk (78 MB)
Feature:
By default, this module enables the chat head feature.
If your device have chat head but you want to use bubble,
- Open messenger app and go to its setting page.
- Click on the toggle icon from the top-right corner.
- Choose bubble option from the pop-up dialog.
[If you want to hide the toggle icon, long press on it and remove.]
_____________________________________________________
Are you wondering whether it is safe to use?
Spoiler: Read Safety Note
Is it safe to use?
This whole project is open source. So, yeah, it is safe, just like any other app installed from the playstore.
[Make sure you installed the MRVPatch Manager from the official github link]
Is it safe for your Facebook account?
Absolutely, that's why you need to install ChatHeadEnabler. It enables chathead in a clean way with a method provided by Facebook internally.
What safety measures are taken for apk files?
The manager downloads your selected app from various apk servers and verifies it against the original facebook signature, which makes sure you are patching an official app pulled from the playstore. It will prevent you from installing any unsafe apps if the verification process is failed.
Spoiler: Problems and Solutions
Note: This patch doesn't mess with original messenger code, that means any feature related bug you experience is probably from messenger itself (or maybe from your ROM). You should try different messenger versions in that case.
If something is wrong with the patch, it will crash or simply chat head will not work.
Here are some known issues that are not caused by this patch:
-> Screen freezes for 1-2 seconds whenever interact with chat head?
This is due to security restriction of A12.
Solution (PC Required):
-> Go to "Developer options". (find from your phone Settings)
-> Enable "USB debugging" option
-> Enable "USB debugging (Security settings)" option [for MIUI].
-> Run this adb command from PC:
Code:
adb shell settings put global block_untrusted_touches 0
[If you don't know how to use adb command, please find a tutorial from xda or youtube]
-> Facebook links are not opening in facebook app?
Solution (PC Required):
-> Go to "Developer options". (find from your phone Settings)
-> Enable "USB debugging" option
-> Run this adb command from PC:
Code:
adb shell pm set-app-links --package com.facebook.katana 1 all
Spoiler: PC Patching Instructions
Instructions:
- Download MRVPatcher-5.5.2.jar
- Download and Install Java JDK 11+
- Download Messenger apk from ApkMirror [1]
- Move MRVPatcher and Messenger to a separate folder.
- Open terminal (or cmd) on that folder.
- Run command: [2]
Code:
java -jar MRVPatcher-5.5.2.jar Messenger.apk
- A new file Messenger-mrv.apk will be produced.
- Follow the same instructions for any other facebook apps.
[1]: Do not download aplha/beta version from ApkMirror.
[2]: To sign with your own key, use -ks option.
[+]: For more info, run java -jar MRVPatcher-5.5.2.jar -h
Source code: MRVPatcher
Source code: ChatHeadEnabler
Source code: MRVPatchManager
This is the only method I found where chat head works on all landscape direction mode. Also finally external sharing problem solved. Thanks.
Facebook lite please
n_boy86 said:
Facebook lite please
Click to expand...
Click to collapse
Attached.
NeonOrbit said:
Let me know if everything works, I didn't test.
Click to expand...
Click to collapse
Thank u very much
I have found you dont even need an alternate app, just go to your phone settings find display over other apps and enable it for messenger. You will automatically get chat heads instead of Bubbles
XxZedlingxX said:
I have found you dont even need an alternate app, just go to your phone settings find display over other apps and enable it for messenger. You will automatically get chat heads instead of Bubbles
Click to expand...
Click to collapse
That's not the case for everyone.
removed
NeonOrbit said:
whoever got back chat head automatically, is it still chat head or returned to bubble again?
Click to expand...
Click to collapse
I'm on OnePlus N10 5G, I get bubbles no matter what from play store version, your patched apk works perfect and I get chat heads back
loinmin said:
I'm on OnePlus N10 5G, I get bubbles no matter what from play store version, your patched apk works perfect and I get chat heads back
Click to expand...
Click to collapse
Thanks for the feedback.
NeonOrbit said:
whoever got back chat head automatically, is it still chat head or returned to bubble again?
Click to expand...
Click to collapse
I'm using Poco F3 MIUI 12.5.4.0 and "Display over other apps" doesn't do anything for me. I have to use the patched apk.
Use Facebook lite or messenger lite...
removed
Hello,try this:
-open Messenger
-tap on your profile (top left)
-scroll down
-enable Chat Heads toggle
This worked thanks alot! I hope you will push to create the app that you mentioned that would patch(one click) the latest fb and messenger app.
So that we'll still have the latest versions of the apps(fb & messenger) while maintaining the chat head function.
All while waiting for messenger to fix it with android 11.
aBetterAndroid. said:
Hello,try this:
-open Messenger
-tap on your profile (top left)
-scroll down
-enable Chat Heads toggle
Click to expand...
Click to collapse
No, the OEM Messenger doesn't work for me. I'm still using the patched one.
Hello, it appears Messenger (332.0.0.11.117) does not patch correctly using the Self Patching Instructions.
(infinite crashing loop upon startup, must revert to self patched Messenger (330.0.0.12.116)
Messenger (332.0.0.11.117) - September 29, 2021.
Messenger (330.0.0.12.116) - September 21, 2021.
I am able to patch the new Facebook (337.0.0.32.118) properly with no issues at all, it seems the newest Messenger update has been /Zuckerburged/.
I am currently running Messenger (330.0.0.12.116) just fine with no issues (minus the weird chat head cropping issues that I believe is just facebook being facebook). - issue occurs on my siblings Samsung s10+ (native chat heads)
I am unsure what to do as I am only reporting an issue and have tried installing it different methods which simply do not work with Messenger (332.0.0.11.117) - September 29, 2021.
as a result I am sticking with Messenger (330.0.0.12.116) - September 21, 2021. (working)
UNTIL FACEBOOK FORCE REMOVES THE EDITING BUTTON DUE TO "OUTDATED" APP.
Thank you for your hard work, it is much appreciated!
loinmin said:
Hello, it appears Messenger (332.0.0.11.117) does not patch correctly using the Self Patching Instructions.
(infinite crashing loop upon startup, must revert to self patched Messenger (330.0.0.12.116)
Click to expand...
Click to collapse
did you patch on Windows?
NeonOrbit said:
did you patch on Windows?
Click to expand...
Click to collapse
Yes, this is the first time it has happened.
It will not work at all beyond Messenger (330.0.0.12.116).
I am unsure of the cause.
I patch through PowerShell as Command Prompt sometimes throws zipping errors. (but seems to patch fine)
loinmin said:
I patch through PowerShell as Command Prompt sometimes throws zipping errors. (but seems to patch fine)
Click to expand...
Click to collapse
It might be due to weird file naming system of Windows.
Check new version of the tool.
I used a new signing key in this version, so make sure to uninstall all fb apps first. (just this time)

[ROM][11][flox][OFFICIAL] crDroid 7.31Google Nexus 7 2013 repartitioned

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/mantinan/android_kernel_google_msm
Device: https://github.com/LineageOS/android_device_asus_flox
Download:
ROM
Known issues:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
bestiatester said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
ROM (Download from here)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Download:
ROM
Known issues:
Battery is shown as charging at 0 mA.
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
Mr.Conkel said:
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
Click to expand...
Click to collapse
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
GeekyTanuj said:
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
Click to expand...
Click to collapse
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Mr.Conkel said:
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Click to expand...
Click to collapse
Thanks for this guide! Really helped me get things going smoothly! Love this ROM.
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
jojo33680 said:
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
Click to expand...
Click to collapse
you need to use the Exkernel to enable dt2w. Here's the latest one: Link.
I am running an old 7.0 Resurrection ROM on my N7.
TWRP is installed & bootloader unlocked so I suspect I would just need to repartition & install?
No clue why ADBgives me these errors in powershell.
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
For those who have partition with a different method like me that is NOT flox so they can flash other ROMs, replace this in the ROM zip. All I did was remove assert get prop that checks to make sure your tablet is the right one for the ROM. It won't flash if you're not using flox repartition so I changed it to allow it to flash. I have 1.6gb of system space and am able to flash this ROM, opengapps pico, magisk and custom kernel with no issues running a non flox repartition.
updater-script
drive.google.com
Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.
bestiatester said:
Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.
Click to expand...
Click to collapse
I confirm I have the same problem
Hello all,
I follow the guides and the installation went smoothly, thanks for the really good job you've done.
I'm new in the crDroid world so sorry if the question seems stupid: As the power button of the Nexus 7 is not easy to access, how can I activate the double tap to wakeup ?
Some years ago the tablet was installed with aicp, and the DT2W was working. So I'm a little bit disappointed if it is not working now.
Thanks.
Davidtre07 said:
DT2W
Click to expand...
Click to collapse
This material will help you: 01 ... 02 ... 03 ... 04
lyushiK said:
This material will help you: 01 ... 02 ... 03 ... 04
Click to expand...
Click to collapse
With Anykernel installed works like a charm !
Thanks.
Davidtre07 said:
With Anykernel installed works like a charm !
Thanks.
Click to expand...
Click to collapse
If you have a patch or pointer to the code that makes it work... just let me know and I'll try to add it.
I'm testing a patch for the charge current to be shown ok, seems to work, if all the tests are ok I'll ship it in with the next release.
No I don't have any patch to propose, I just followed the links provided by @lyushiK.
As far I understood, to work you have to recompile a kernel with DT2W hability and you have to activate it with the right flag in the kernel.
From my side what I've done:
Installed Magisk (patched boot.img)
Installed this kernel: https://androidfilehost.com/?fid=7161016148664820402
And to finish added to magisk this module: https://github.com/ipdev99/mModule_dt2w
Reboot and it works !
In Magisk I see the module is looking in /sys/ for "doubletap*" or "dt2w*" or "wake_gesture".
If it found one of the files then activate it (echo 1 in the file)
But still, you have to have the right kernel !
Thanks very much, this Rom is so smooth and running great. The only thing I've noticed is that the icon size and text is very small when using the tablet in landscape mode but fine in portrait mode. Any changes I make to the icon size from the settings apply in portrait but when switched to landscape stay as really small, is there any setting I have missed to enlarge them?
Thank you for the great work!
Just for feedback: I can confirm the camera issue, too, though it doesn't bother me.
Another small thing I noticed: during the initial setup my device was called Pixel 6 Pro (first I thought, I chose the wrong image) but in the settings it says correctly "Nexus 7".

[ROM][13.0_r49][pyxis][OFFICIAL] Evolution X

Evolution X 7.6 for the Xiaomi Mi 9 Lite [pyxis]
Code:
/*
* Your warranty is void. Or valId, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
{
"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"
}
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@RealAkito
@AnierinB
Reach us on Twitter! @EvolutionXROM
Just flash and check "The Evolver". We have tons of features combined together from different ROMs.
* You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
instructions on #Post 3
Download
Donate to me! / Official Chat / Device Support
​
Android OS version: 13
Security patch level: May 2023
Build author: Czarsuperstar
Source code: https://github.com/Evolution-X
Kernel Source code: https://github.com/LineageOS/android_kernel_xiaomi_sdm710/tree/lineage-20
ROM Developer: Joey Huab
XDA: DevDB Information
Evolution X, ROM for the Xiaomi Mi 9 Lite
Contributors
Czarsuperstar
Source Code: https://github.com/Evolution-X
ROM OS Version: Android 13
ROM Kernel: Linux 4.9.335
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.9.2
Stable Release Date:
Created 2022-12-29
Last Updated 2023-06-10
his is Android 13 with May 2023 (r49) security patches
Notes:
==============================
- Always dirty flash at your own risk.
- We're not responsible for any issues that this may cause.
- Clean Flash is always recommended
Device changes:
==============================
None
------------------------------
ROM changes:
==============================
6/10
AttestationHooks: Un-spoof GMS while adding google account
overlay: Switch to AttestationHooks for spoofing
6/8
Evolver: Disable some notification and media control features
GnssLocationProvider: Implement xtra-daemon toggle
SystemUI: Prevent edge lights from being directly shown by screen on and notification callbacks
6/7
ApplicationPackageManager: Adjust Tensor workaround
PixelPropsUtils: OP9R > OP9P
PixelPropsUtils: Switch Honor of Kings hide to Xiaomi 13 Pro (China)
PixelPropsUtils: Use OP9 PRO for LOLM
SoundSearchTile: Do not use Shazam
6/6
Avoid NetworkPolicyLogger NullPointException
Hide data limit notfication if data not active nor default
Ignore BIND_ABOVE_CLIENT for same-process connections
Request correct rendering type for EGL config
fixup! fw/b: Add support for allowing/disallowing apps on cellular, vpn and wifi networks
6/5
Add listener once for volume row animation
Launcher3: Implement hidden & protected apps
Launcher3: Improve hidden & protected apps
Launcher3: Switch to AppLock API for protected apps
Launcher3: Reload icon pack settings fragment on resume
Launcher3: Update AppLock API and integrate hidden apps
SystemUI: Introduce preferred network tile
SystemUI: Restore try-finally condition when reinflating QS panel
VolumeDialogImpl: Reconfigure handling of animation/jank listeners
base: Minor improvement to the PowerOffAlarmService body string
core: Catch OOB when returning pooled string
themes: Add more Icon Shapes from Iconify
themes: Import more signal & wifi icons
6/4
PixelPropsUtils: Switch Honor of Kings spoof to Redmi K30 Ultra
Settings: Hide ADB and developer setting enable status
rro_overlays: Unset config for QR code scanner
6/3
Evolver: Bring back support for Parallel space
Evolver: Improve brightness slider themes layout
Improve support for brightness slider themes
Settings: Add support for parallel space
SystemUI: Clean up battery callback in CollapsedStatusBar
SystemUI: Switch to TunerService for CollapsedStatusBar
packages: Bring back Parallel space
rro_overlays: Don't force disable Adaptive sleep for Pixel devices
themes: Add category for brightness slider themes
6/2
InfoBottomSheet: Fix black screen when clicking source pref
Launcher3: Adjust icons on dock search bar
Launcher3: Apply corner radius setting for app search bar
Launcher3: Directly open Pixel Search if installed
Launcher3: Fix all apps SB's google icon touch detection
Launcher3: Fix bottomsheet info pref alignments
Launcher3: Improve paddings for all apps search bar
Launcher3: Improve search bar header protection
Launcher3: Match app search bar theme with dock search bar
Launcher3: Prioritize pixel search for QSB instead of Google app
Launcher3: Reduce search bar hint text size
Launcher3: Refactor all apps search bar functionality
Launcher3: Restart launcher on pixel search change
Launcher3: Rework QSB and all apps search bar
Launcher3: Search Bar UX-related changes
Launcher3: Show a toast when restarting launcher due to component change
Launcher3: fix app icon font
SystemUI: Improve dismiss all button visibility
SystemUI: Refactor reticker feature
SystemUI: Toggle dismiss all visibility before reticker animates
common: Label ro.vendor.fm.use_audio_session
qcom: Sort sepolicy.mk m4defs
6/1
PixelPropsUtils: Add Gameprops for Battlegrounds Mobile India (BGMI)
SystemUI: Improve QS notification expansion animation
qcom: Drop untrusted app policies
sepolicy: Introduce rw_dir_file()/create_dir_file() macros
5/31
CAMX: CHI: Added support for handling jpeg debug data
Camera: Fix size list parceling
Camera: Ignore torch status update for aux or composite camera
Camera: Support exposing aux camera to apps
camera2 vndk: Improve error handling
CameraManager: Fixup exposing aux camera to apps
CameraManager: Handle NPE with ActivityThread.currentOpPackageName()
Changing max SampleRate limits for raw audio decoder
Import Xiaomi Image Tags definitions
Native: Camera: Import Release Slot Xiaomi Changes
Native: IPCThreadState: Import Xiaomi Modifications
Native: ProducerListener: Import ON_BUFFER_DETACHED Changes
cameraserver: Let multiple cameras opened by stock camera application
gms: Add lynx to whitelist
gms: Update GoogleCamera
gms: Move DeviceIntelligenceNetworkPrebuilt to PRESIGNED
5/30
Add null pointer check to avoid system crash
Settings: Don't allow divider for AOSP DT2W
Settings: Make Ambient Display toggle show on single tap sensor
Settings: Use lottie for AOSP DT2W
SystemUI: Doze: Add config to check proximity on pickup events
SystemUI: Doze: Add config to check proximity on single tap
SystemUI: Prevent edge lightning from pulsing outside keyguard/doze
hwui: Optimize for performance and memory usage
themes: Configure font spacing for more clock fonts
5/29
ApplicationPackageManager: Extend freeform window feature to all apps
ApplicationPackageManager: Remove p21 features from featuresPixel
Pre-grant non-system preloaded apps
core: block 2021/22 pixel features to ASI and pixel launcher
5/28
AttestationHooks: Allow spoofing device model for Netflix
Enable copying content for IMEI2
Evolver: add acun and bang brightness slider
Fix NullPointerException in GestureDetector
Increase 5 GHz network signal tolerance
Launcher3: Fix quickstep live tile implementation
Installing a custom recovery using fastboot​
Download Evolution X Recovery. Simply download the latest recovery file, named something like evolution_pyxis-ota-tq1a.230205.002-02070633-unsigned.img.
warning
IMPORTANT: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
Connect your device to your PC via USB if it isn’t already.
If your device isn’t already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
check
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Now reboot into recovery to verify the installation. Do not reboot into the existing OS, since it will overwrite the recovery you just installed!
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
NOTE: If you can’t power down the device, try long-pressing the key-combination (if any was used in the instructions above) until the device reboots and follow the instructions above
Installing Evolution X from recovery​
Download the Evolution X installation package that you would like to install.
You will also need to flash an empty super image since your device uses retrofitted dynamic partitions: download super_empty.img from the directory named with the latest date here
Install instructions Taken from Lineage install instructions for Pyxis and edited for install instructions for Evolution X on Pyxis. All credits to @ceracz for his incredible work on the Pyxis. Thank you.
Reservation​
Congratulations,
Thanks for your great work, to put pyxis official.
Have a nice year.
Thx works perfect
Default AOD looks ugly. For Pixel like AOD select Google Sans Font and it's looks perfect
Update is live Guys
I tried this ROM on my Mi 9 Lite and everything works with the exception of the unreliable in-display fingerprint. But otherwise it's a solid ROM and oh boy, that makes it feel like a Pixel phone with more features than the real Pixel!
Thanks for your hard work!
Guys this is my first rom I installed on my Mi 9 lite and i have to say im blown away
Solid material UI clean stock Android im speechless
Thanks for your hard work
But i have a question
At first when i installed the rom i wasn't able to boot into system i was always send to recovery (TWRP)
Then I tried to install LineageOS i flashed their recovery then i fashed their rom (i don't know if it was flashed correctly or not)
Then i restart the device and i was booted into EvolutionX rom
Can anyone tell me what happened?
Mr Trigger said:
Guys this is my first rom I installed on my Mi 9 lite and i have to say im blown away
Solid material UI clean stock Android im speechless
Thanks for your hard work
But i have a question
At first when i installed the rom i wasn't able to boot into system i was always send to recovery (TWRP)
Then I tried to install LineageOS i flashed their recovery then i fashed their rom (i don't know if it was flashed correctly or not)
Then i restart the device and i was booted into EvolutionX rom
Can anyone tell me what happened?
Click to expand...
Click to collapse
Because Los is using dynamic partitions Evolution X is not.
[email protected] said:
Because Los is using dynamic partitions Evolution X is not.
Click to expand...
Click to collapse
but how i booted into EvolutionX?
Mr Trigger said:
but how i booted into EvolutionX?
Click to expand...
Click to collapse
I'm not sure but if it's working then no worries.
Update is Live Guys.
My phone keeps booting to Recovery.
I downloaded the update and tried to install OTA. I couldn't remember if I used twrp or not because it's been so long since there was an update. It didn't work.
I tried doing a clean flash following the instructions above and I'm still being booted to the recovery.
Is there something I can do to fix this?
Mr Trigger said:
Guys this is my first rom I installed on my Mi 9 lite and i have to say im blown away
Solid material UI clean stock Android im speechless
Thanks for your hard work
But i have a question
At first when i installed the rom i wasn't able to boot into system i was always send to recovery (TWRP)
Then I tried to install LineageOS i flashed their recovery then i fashed their rom (i don't know if it was flashed correctly or not)
Then i restart the device and i was booted into EvolutionX rom
Can anyone tell me what happened?
Click to expand...
Click to collapse
Can you send me a copy or link to download lineage OS? I'm having the same problem with booting into recovery. Maybe it will help me.
I<3cats said:
My phone keeps booting to Recovery.
I downloaded the update and tried to install OTA. I couldn't remember if I used twrp or not because it's been so long since there was an update. It didn't work.
I tried doing a clean flash following the instructions above and I'm still being booted to the recovery.
Is there something I can do to fix this?
Click to expand...
Click to collapse
Hey, I have the same issues in the past every time I flash a new rom. You have to flash the VBMETA PATCHER for our device.
You can find link'n'stuff here.
In few words the vbmeta check that there have been no tampering inside the "boot", "System" and "Vendor" partitions. So without its replacement, following the flash of .zip packages, the device may not be able to start the ROM and go to Bootloop.
Marko Indaco said:
Hey, I have the same issues in the past every time I flash a new rom. You have to flash the VBMETA PATCHER for our device.
You can find link'n'stuff here.
In few words the vbmeta check that there have been no tampering inside the "boot", "System" and "Vendor" partitions. So without its replacement, following the flash of .zip packages, the device may not be able to start the ROM and go to Bootloop.
Click to expand...
Click to collapse
Thanks, but now I'm in worse shape. lol I bricked my phone. It only boots to fast boot.
I found a tutorial to help, but I'm having difficulty using the solution because it's for people using WIndows, not Linux. I'm not well versed with using the Linux terminal and having trouble using adb tools. Windows in the sandbox isn't working for some reason. I downloaded a new Windows ISO image but I'm getting messages in the sanbox about no bootable disk.
Hey
I<3cats said:
Can you send me a copy or link to download lineage OS? I'm having the same problem with booting into recovery. Maybe it will help me
Click to expand...
Click to collapse
Hey partner
I downloaded this rom ( https://mirrorbits.lineageos.org/full/pyxis/20221224/lineage-19.1-20221224-nightly-pyxis-signed.zip )
This recovery ( https://mirrorbits.lineageos.org/recovery/pyxis/20221224/lineage-19.1-20221224-recovery-pyxis.img )
This super empty image ( https://mirror.math.princeton.edu/pub/lineageos/full/pyxis/20221224/ )
And followed the installation steps from here ( https://wiki.lineageos.org/devices/pyxis/install ) till step 6 where you will sideload the rom
That's all I did then I reboot the phone and it booted to EvolutionX
P.S
The flash of super empty image maybe it will just shown "Searching for devices" or something like this in ADB. Just press Ctrl+C and continue forward
I<3cats said:
My phone keeps booting to Recovery.
I downloaded the update and tried to install OTA. I couldn't remember if I used twrp or not because it's been so long since there was an update. It didn't work.
I tried doing a clean flash following the instructions above and I'm still being booted to the recovery.
Is there something I can do to fix this?
Click to expand...
Click to collapse
Are you clean flashing? Format Data=yes
I<3cats said:
Thanks, but now I'm in worse shape. lol I bricked my phone. It only boots to fast boot.
I found a tutorial to help, but I'm having difficulty using the solution because it's for people using WIndows, not Linux. I'm not well versed with using the Linux terminal and having trouble using adb tools. Windows in the sandbox isn't working for some reason. I downloaded a new Windows ISO image but I'm getting messages in the sanbox about no bootable disk.
Click to expand...
Click to collapse
Hi, as @[email protected] said you need to do a clean flash and:
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Here you can find a useful Linux adb command list. (commands are pretty much WIndows likely)
PS
Try to load TWRP from fastboot: adb reboot recovery
IMPORTANT: While you are in Fastboot be sure that phone is charged

Categories

Resources