┤Mod Edit├┤Closing note. YouTube Vanced lives on in ReVanced (not affiliated with Vanced)├
Before asking or posting anything, please read the first and second posts.
Always check the official Vanced website or XDA thread when downloading. Other sites are fake, contain advertisements (possibly even malware), and have older versions.
{
"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"
}
Vanced is a well-known modded version of the YouTube app with many features such as ad-blocking and background playback. Vanced also offers some extra features to enhance the user experience. The entire list is available below:
Features:
Vanced IS NOT YouTube Premium
Blocks all YouTube ADs (some options are togglable)
Background playback feature
Force VP9(or HDR) or vice versa
Override Max Resolution
Casting togglable (can be forced off)
Togglable Theme (White/Dark or White/Black)
Picture-in-Picture mode(PIP) (Android 8.0+)
Video window new or old style
Repeat video feature
Preferred Resolution & Speed feature
Swipe controls for Volume and Brightness
Sponsorblock integration
Return YouTube dislike integration (ALPHA)
Tap to seek feature
Copy video link + with timestamps feature
New Logo by @Logan
[Optional] Detach YouTube from play store for Root users
INSTALLATION INSTRUCTIONS:Since YouTube v14.41.52, Google has moved to split APKs format. The Android package installer doesn't support Split apks yet, so we are now using Vanced manager for installing all vanced apps. The steps to use the vanced manager are below:Especially for MIUI, there's a separate guide that can be accessed using this link. For all other devices, please follow below:
For Non-Root:
Install Vanced Manager
Open Vanced Manager and tap the blue arrow in the lower right corner.
Begin installing Vanced microG. (Without which you won't be able to install Vanced (or Music Vanced) or use login)
Then install Vanced (or Music Vanced), log in to your account and enjoy!
For Root:
Install Vanced Manager
Open Vanced manager and tap on the "Magisk" icon to grant root permissions.
Once you are in, begin installing Vanced (or Music Vanced).
Important information:
We replaced our root installation with vanced manager, which directly mounts vanced on top of Youtube in the /data/app directory, making it easier and faster than before.
Vanced will not block ads while casting since when you use the casting feature, it doesn't send the video from your phone to the Chromecast/TV. Instead, your phone acts like a remote controller for the youtube app in your Chromecast/TV. That is why the advertisement is displayed.
Purchasing items in the non-root version of the app will not work as microG doesn't support it. Hence, it is preferable to use the original YouTube app or using the web version for any purchase.
If your videos are lagging or the application starts to crash while watching live videos, please enable VP9 codec from codec override present under vanced settings. Google forced the ExoPlayer v2, which is highly experimental and unstable on unsupported devices.
YouTube has dropped support for Android 5 (Lollipop) with v17.xx.xx. Hence, the minimum supported version is now Android 6 and above.
Known bugs:
Swipe down gesture for refreshing home feed breaks randomly. It's an issue with litho that only Google can fix. There's nothing we can do to fix it. (Tap here to learn more)
As of v16.16.38, casting won't work due to an upstream microG bug. (Tap here to learn more)
On portrait/vertical videos, preferred quality options do not work.
Swipe controls triggers when swiping either upwards or downwards to scroll through description or in live chat when in landscape mode.
On new action bar layouts(server-sided feature), the new toggles won't work.
Info cards toggle is broken (Temp fix: Disable it through your Google account settings. This setting disables info cards everywhere.)
App crashes with java.lang.ExceptionInInitializerError while playing some video outside of vanced.
Manual codec override is broken and very experimental.
Some users might face geographical ads on YouTube Shorts tab.
SponsorBlock segments at the end of videos in playlists causes playback on the next video to start where the previous one ended.
Social links
Vanced official Website: https://vancedapp.com
Telegram Channel: https://telegram.me/vanced
Discord Server: https://vancedapp.com/discord
GitHub Repository: https://github.com/TeamVanced
Reddit: https://www.reddit.com/r/Vanced/
Thread Managed by @ZaneZam, @Razerman, @KevinX8 and @laura almeida
BUG Reports:
Steps to do before reporting a bug:
Do a search and see if it has already been reported
Check that the bug is actually a Vanced bug and doesn't happen in the original YouTube.
Steps to do when reporting a bug:
Make sure you are being enough descriptive of the problem.
Take a logcat (Google search if you don't know how). Especially if the issue is a crash.
Taking pictures of the problem doesn't hurt.
If the report is vague (missing information), it will most likely just be ignored. If you are not going to show any effort in resolving the problem, why should I?
Bug report template:
Vanced exact version number (Do NOT say latest).
Download link used to download Vanced.
Installation method (whether user SAI or Vanced Manager)
Device.
ROM (optional may not help).
Any applied Substratum/swift overlays.
Logs if there are any crashes/force closes (upload to Pastebin or hastebin or katbin) and paste the link of it with your report. [Check here to know how to get logs]
A brief description of the issue
Any installed mods to the system.
Test your issue on the stock youtube app
Important links:
Installation guides
Vanced MIUI Installation guide
Frequently Asked Questions (F.A.Q)
Vanced troubleshooting
Vanced v17.03.38 troubleshooting
Bugreport & logcat Guide
Downloads:
Vanced
The official website of Vanced - a Video client for Android (Not affiliated with Google/YouTube).
vancedapp.com
Alternative Mirrors for pre 15.x: AFH Mediafire
Good job guys!
Non-root FAQ:
https://forum.xda-developers.com/showpost.php?p=79661381&postcount=10743
Microphone permission not found:
If you're wondering why there is no microphone permission in the root version of Vanced, that's because the APK used to modify Vanced (minAPI17) is missing the microphone permission. The other APK has it (minAPI21) but that lacks the translation. Why? Ask Google ?*
Workaround: use the non-root variant, or stock YouTube
App not appearing in app drawer:
If YT Vanced app is not visible in your app drawer, follow these steps:
• Install regular YouTube app from the Google Play Store
• Open the app until your front page shows up (not sure if this is necessary. Just reconstructing what's been working for others all the time).
• Go to Settings > Apps > YouTube. It should show "Uninstall" on the top left. DO NOT Uninstall! Just see if it says that there!
• Reboot
• Go to Settings > Apps > YouTube. Now it should say "Disable" or "Deactivate". DO NOT Uninstall! Just see if it says that there!
• In the same menu; tap on the three dot menu button on the upper right corner and tap on "Remove/Uninstall Updates".
Now the YT Vanced app should show in your launcher.
OR
For appdrawer issues, follow
stuck at splashscreen:
https://forum.xda-developers.com/showpost.php?p=81740301&postcount=13953
who got issues and want to do a proper report its mentioned in 2nd post at the OP or you can follow this template:
BUG REPORTS (all details MUST be included or your report will be ignored):
1. YouTube Vanced exact version number (Do NOT say latest).
2. Download link used.
3. Installation method.
4. Device.
5. ROM (optional may not help).
6. Any applied Substratum overlays.
7. Logs if any (upload to del.dog or Pastebin.com)
8. A brief description of the issue
9. Any installed mods to the system.
(There is alot of threads shows how to capture logcat around xda)
Love you guys ?
magisk repo is not updated yet
Freshly clean sheet! good job guys!:highfive:
Installer still 2.8 ?
Great...
Magisk not there yet...
Updater process ended with ERROR: 1
Error installing zip file ´/external_sd/iYTBP-vanced-universal-installer-v2.8.zip
What am I doing wrong?
okeck22 said:
Updater process ended with ERROR: 1
Error installing zip file ´/external_sd/iYTBP-vanced-universal-installer-v2.8.zip
What am I doing wrong?
Click to expand...
Click to collapse
Try making sure system is checked under mount in TWRP. If that's already I checked I found rebooting to recovery over and over till it isn't all correctly also works. I think it's just some kind of bug with TWRP.
Magisk repo not updated yet
Yey, I was expecting for this, thanks and keep it up guys, awesome.
michael_0394 said:
Try making sure system is checked under mount in TWRP. If that's already I checked I found rebooting to recovery over and over till it isn't all correctly also works. I think it's just some kind of bug with TWRP.
Click to expand...
Click to collapse
THX for the advice, sadly it didnt help at all...
okeck22 said:
THX for the advice, sadly it didnt help at all...
Click to expand...
Click to collapse
When I tried flash it few days ago, twrp showed me "apk file doesn't exist". Check how mb has this zip. You should install it via magisk or create in system/app, "YouTube" folder and give it 755 permissions. Next move YouTube.apk file to this folder and give it 644 permissions. Last step is reboot.
Xiaomi Redmi Note 4X Resurrection Remix 6.0.0 Tapatalk
Zgadnijcie said:
When I tried flash it few days ago, twrp showed me "apk file doesn't exist". Check how mb has this zip. You should install it via magisk or create in system/app, "YouTube" folder and give it 755 permissions. Next move YouTube.apk file to this folder and give it 644 permissions. Last step is reboot.
Xiaomi Redmi Note 4X Resurrection Remix 6.0.0 Tapatalk
Click to expand...
Click to collapse
I installed Vanced-ARM64-Black-13.07.55.zip <---Magisk Modul, did a reboot setup the app, then again flashed in TWRP with edited settings.sh and "dark" apk
All working fine now - BIG THX
okeck22 said:
Updater process ended with ERROR: 1
Error installing zip file ´/external_sd/iYTBP-vanced-universal-installer-v2.8.zip
What am I doing wrong?
Click to expand...
Click to collapse
Do you have the APK in internal storage? Probably should put the zip there too?
Did you unzip and rezip by any chance?
Thanks! Installed magisk module black, but apparently it's white.
Related
========================================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.
{DEPRECATED}
This project won't release a new version because I see no reason for that since modified lib v.2.3 is working fine on OP5/5T without breaking OOS functionality.
Hi guys,
After intensive try. I’ll glad to tell you that I just found the way to fix GCam Front facing camera portrait mode without using Magisk module. (which break Face Unlock functionality in OOS)
Instead, my method will dynamic change library only when needs to use GCam and you can revert to default binary, then you still can use Face Unlock.
THIS MOD WAS TESTED WITH OXYGEN OS OREO ONLY
Warning:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, your phone won’t boot. Use it at your own risk
Prerequisite:
1. Root with Magisk (My app/script only test with Magisk)
2. Busybox NDK (Magisk Module)
3. My file.
4. Disable all lib fix module. (prevent confliction)
5. Recommended Gcam APK: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/
How to:
Ver 3.5.1
1. Download my file here View attachment FixGCam-by-aillez-Unified-V.3.5.1.zip and don't move to another folder. (should be in Download folder or XDA folder)
2. Install this app from the archive (FixGCam-by-aillez-Unified-V.3.5.zip)
3. Allow storage permission of my app. Long Press the app and choose App info > Permission > Storage > Enable it.
{
"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"
}
4. Open the app and tab Read me/Tutorial button and read it first.
5. Tab Create required file button.
6. Wait until it shows toast about "Required file has been created"
7. Auto-Mode is Fix binary and automatic revert after screen off. (It'll ask for root permission)
8. Manual Fix and Revert is for a user who wants to trigger it by their design time. (It'll ask for root permission)
9. Pick GCam dialog will show after you fix binary (either Auto-Mode or Manual) PS. Only supported for Pixel2Mod and Pixel3Mod by Arnova8G2
10. If you think this mod helps your life better and it worth for some donation. Please help donate
Troubleshooting.
1. If you get "Archive not found" when tab Create required file >>> Download My file first.
2. If you get "You don't have a required file" >>> Tab Create required file button.
3. If you get "Busybox not found" >> Install it.
4. If Create required file doesn't say anything to you. (report by some users).
You need to create a folder name "FixGCam-by-aillez" in internal storage and extract file from archive to there. (As a workaround) Folder structure should be like this.
and you should not tab Create required file.
5. After I fix binary Gcam still don't work/Capture Pink image. What should I do?
Sometimes Gcam already running before change library and load default binary. Fc Gcam and try again will help.
Updated: Should be fixed in V.3.5.1
---------------------------------------------------------------------------------------------------------------------------------------------------------default-----------------------------------------------------
Code:
Tutorial + Demo for V.3.0
[media=youtube]aelumI-U7AM[/media]
Ver. 3.0
1. Download My file here [ATTACH]4503243._xfImport[/ATTACH]
2. Extract it to your root of internal storage (/storage/emulated/0) [U][B]otherwise my script won’t work.[/B][/U]
3. Looking for App folder you will find 2 APK. Install it.
4. When you need to use GCam.[B] [U]Launch 01_FixBinary_by_aillez app[/U][/B]. Give it root permission and wait for it to say "GCam Binary is Fixed"
5. If GCam still take Pink image. Force close GCam and try again.
6. When you done using GCam. [B][U]Launch 02_02_RevertBinary_by_aillez app. [/U][/B] Give it root permission and and wait for it to say "Reverted to Stock Binary Completed".
7. Enjoy using Face Unlock, OOS Cam all functionality.
That’s it. Enjoy
All credit goes to who made this happen
@defcomg (SavitarZA) for Portrait Fix binary.
@topjohnwu for Magisk
@osm0sis for Busybox Systemless
@txx1219 for his finding of solution for camera2api
@Arnova8G2 for Dot fix and GCam Mod.
Not necessary but If you like my work and wanna buy me some coffee.
Donation: https://www.paypal.me/aillez
Changelog:
V.2 - Added SManager method.
V.2.1 - Repack for new binary to use with OOS 5.1.x (Android 8.1)
V.2.2 - Repack new dotfix lib by Arnova8G2 and colour fix lib by Savitar (aka Defcomg).
V.3.0 - Big Update....Release as an app. No more Tasker and SManagers thing.
V.3.5 - Combine 2 APK to 1 APK (from V.3.0)
Added Application interface.
Bring back automatic mode and added create required file.
Added Pick GCam version dialog after fix binary (Pixel2Mod and Pixel3Mod)
Added error-handling. Should be easier to know what wrong and how to fix it.
V.3.5.1 - Updated lib from Arnova8G2 v. 2.2
Added loop for Force close Gcam after fix binary (should solved all pink image after fix binary)
Thank you I will try this mod.
(Glad to see Thai people here.):fingers-crossed:
The YouTube video is not working
ps000000 said:
Thank you I will try this mod.
(Glad to see Thai people here.):fingers-crossed:
Click to expand...
Click to collapse
Greetings!!
arun483 said:
The YouTube video is not working
Click to expand...
Click to collapse
Can you try this link?
how do I Import project??please make a step by step video of how to install or atleast write a step by step guide please
Hey! It works amazingly well....
So, I was thinking about triggering the revert task to exiting Gcam rather than screen off. The only problem is that it detects exiting Gcam if you go view your photos from within the camera app. I can't figure out how to make it work. Anyone with more Tasker knowledge know how to make this work... I.e. tie the fix to launching the app, then get it to revert on closing the app? I know there are downsides either way really.
Working great! Thanks ?
Th3PorTuGa said:
Working great! Thanks ?
Click to expand...
Click to collapse
please tell me a step to step guide
aneesh12 said:
please tell me a step to step guide
Click to expand...
Click to collapse
Install the busy box module
Restart the phone
Install Tasker
Go to Tasker options and disable beginner mode
Download the zip provided by the op and extract it
Go to Tasker and create a new project and select the files in the zip
Start the project
Done
Th3PorTuGa said:
Install the busy box module
Restart the phone
Install Tasker
Go to Tasker options and disable beginner mode
Download the zip provided by the op and extract it
Go to Tasker and create a new project and select the files in the zip
Start the project
Done
Click to expand...
Click to collapse
how do i place a shortcut in my home screen?
aneesh12 said:
please tell me a step to step guide
Click to expand...
Click to collapse
aneesh12 said:
how do i place a shortcut in my home screen?
Click to expand...
Click to collapse
Add a widget
Th3PorTuGa said:
Add a widget
Click to expand...
Click to collapse
I use Nova launcher and I've set it so that if I swipe over the Gcam icon, it launches the Tasker fix. I modified the Tasker fix to launch the app after it successfully patches. So to run Gcam I swipe. To use it again before I turn off the screen I just tap the icon.
in my case the camera app doesn't take any picture in portrait mode with the front camera
No errors when the task is execute and works well the restore for the face unlock...but I can't take the photo
OB3 + Arnova's v6_beta15
EDIT: It's necessary to enabled hdr+ front camera
Thank you very much man I really prefer face unlock over fingerprint and I often use my camera (thank God we have gcam to replace stock camera) and it was a pain to have to reboot to get either gcam or face unlock.
It's working for me on OB3 with arnova Cam and other version of gcam.
Good to see it's working for you
I'll try to write a script to run without needs of Tasker since not everyone using Tasker.
But I can't give you ETA.
???
aillez said:
Good to see it's working for you
I'll try to write a script to run without needs of Tasker since not everyone using Tasker.
But I can't give you ETA.
Click to expand...
Click to collapse
How about using Tasker App Factory to create an app of your profile which can be used by everyone.
aayushgala said:
How about using Tasker App Factory to create an app of your profile which can be used by everyone.
Click to expand...
Click to collapse
I try but error about parsing package. I think maybe cause by I need to add permission on package but I'm not sure what needs to be add.
aillez said:
Good to see it's working for you
I'll try to write a script to run without needs of Tasker since not everyone using Tasker.
But I can't give you ETA.
???
Click to expand...
Click to collapse
Quick update here.
I finally writing script and keep testing.
NOW SCRIPTS IS COMPLETED.
This will allow users who not using Tasker can using my mod.
Will record tutorial and share here soon :laugh:
aillez said:
Quick update here.
I finally writing script and keep testing.
NOW SCRIPTS IS COMPLETED.
This will allow users who not using Tasker can using my mod.
Will record tutorial and share here soon :laugh:
Click to expand...
Click to collapse
Thx a lot
aillez said:
Quick update here.
I finally writing script and keep testing.
NOW SCRIPTS IS COMPLETED.
This will allow users who not using Tasker can using my mod.
Will record tutorial and share here soon :laugh:
Click to expand...
Click to collapse
thank you so much bro..
Custom firmware for FiiO M6, FiiO M7 and FiiO M9
Hi everone,
My hobby is modding and building ROMs so now I mod FiiO M6 and M7 firmware.
Why? Now you can install playstore and activate third party players like PowerAmp and Neutron or use streaming apps like Spotify or Tidal.
I hope you will enjoy my ROM
Installer Features
Installing MicroGapps and Playstore to download and activate third-party players (Requires my firmware to work)
Magisk Installer (Requires my firmware to work)
Mixplorer (File Manager)
Dark Theme Installing
Xpossed Framework Installer
Optimized Fiio Music App
Optional Tidal Installing
My Firmware Features
Improved sound (Editing system configurations, Alsa, Updated SoundLibs)
Optimized system resources
Magisk (Root)
Activated WiFi item in settings
Updated FiiO Music App
Fake Signatures support
Activated Init.d
Useful build.prop tweaks
Another Bootanimation
Changed font to Russia font (Ubuntu + Samsung One)
And many other improvements
How to install firmware: Youtube Instructions
M7 Firmware link: M7 Firmware
M6 Firmware link: M6 Firmware
M9 Firmware link: M9 Firmware
If you want to thank me financially:
Bitcoin: 1MeMen1FHZ5iut5KYmdJrQKBgk2e8hts7f
Ethereum: 0x4C90b19a78f19a6fbaA191C58cF0E87751588d3c
PayPal: http://paypal.me/antonixo
QIWI: https://my.qiwi.com/Konstantyn-YFrx47iPqT
Installation Instructions
1. Download my firmware and copy it to sd card
2. Go to recovery by off player and turning it on pressing next track and power if you use M7 or volume down and power for M6.
3. Wipe data using vol+ vol- and power buttons select "Wipe data/factory reset" paragraph
4. Press yes and reboot to recovery.
5. Go "Install update from sd card" and select archive with my firmware.
{
"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"
}
6. Now Aroma installer starts. To controll in aroma installer use combination of pressing Power+Vol+ Power+Vol- and Power.
7. Go next page by using Power+Vol+ and select any paragraph you need.
8. Power+Vol+ to start installation.
9. After installation press power and reboot to the system (First loading will take about 3-7 minutes)
FAQA: Player becomes laggy!
B: I cannot fix bad processor of FiiO M7. Lags because you start use player another way. You update FiiO Music, install Playstore. Apps require more performance hardware. Try reinstall with old FiiO Music and without Gapps
A: How to go back to original firmware
B: You can easily go back flashing stock rom for FiiO M7 from here - M7 Firmware or for fiio M6 from here - M6 Firmware. Just flash it from recovery like my firmware
A: Why, when entering Magisk, there is a notification about an additional installation?
B: Since the magisk was installed "by hand", he did not unpack the files he needed to the Data section. To fix the problem without the module and install this module
A: Why is there only only my language in the keyboard?
B: Settings - Language & input - Virtual keyboard - Simple keyboard - Language
Uncheck the system languages and put them in the languages you need
A: Stuck on logo/bootloop!
B: Hold the power and pause button, after the screen turns off, press the button down, in recovery, select Wipe data.
Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?
Mentalmuso said:
Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?
Click to expand...
Click to collapse
Did you select magisk app in installer? You have M6 or M7?
tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.
AntonIXO said:
Did you select magisk app in installer? You have M6 or M7?
Click to expand...
Click to collapse
M6, it seems userdata doesn't mount so the magisk data files don't install. You have the correct platform etc for mounting, but I'm not sure why it fails. Otherwise it all works great.
dubsflyt said:
tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.
Click to expand...
Click to collapse
Flash stock firmware through recovery
AntonIXO said:
Flash stock firmware through recovery
Click to expand...
Click to collapse
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something
dubsflyt said:
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something
Click to expand...
Click to collapse
I've update rom. Try again.
cannot make it work even with new update:-(
unfortunately same result with the new update on the m9
any news?
installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.
Paris333 said:
installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.
Click to expand...
Click to collapse
Go to magisk, press cancel in window and install module from module menu
Please please update for m9...
Any news ?
m9 업데이트 해주세요 ... 제발 ..
Just tried today's version but it dows not install.
after installing statrs after 2 or 3 seconds it reboots
I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.
Admiral_Face said:
I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.
Click to expand...
Click to collapse
try installing magisk manager v7.5.1 , im using that one with success. Getting root access now. I think half of it is actually the super lag we are getting with having play store, i have put together a very stripped down version of the stock firmware, removed a load of useless apps that all take up precious ram. I am simply downloading my preferred streaming app (deezer) and a couple of other useful apps (terminal, root explorer, magisk manager) and storing them all on my ext sdcard to install after clean install. I seem to be having a pretty fluid experience now.
anyone can fix da M9 file? it does not install any file to the device...
[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)
{
"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".