Related
ViPER4Android for Nougat (Android 7)
{
"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 Link: CLICK
Original thread: HERE
You will need root and BusyBox
Have not tested with other than stock kernel.
How to install
Turn off your phone and boot into recovery.
Once your phone boots into recovery, navigate to install section and select*“ViPER4Android_2.5.0.5_guitardedhero.zip”.
Flash it and restart the phone.
When the phone turns on go to Play Store and install a file manager with root access. The best one is ES File Explore and Total Commander.
Open the File Manager and go to*/vendor/etc.Find*a file named*“audio_effects.conf”.*Delete this file or save somewhere just in case you want to revert back.
Now open Viper4Android on your device, and install the driver if it’s required.
Wait for the driver to finish installation and reboot the phone.
That’s all! You have successfully installed Viper4Android on Android 7.0 Nougat.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ViPER4Android Cleaner v1.3 | Android 7.x
Download Link: CLICK
Original thread: HERE
Viper4Android for Android Nougat is out but after installing it I realized that MusicFX is still present in my ROM and V4A is not working inside all apps.
So I have created this simple Viper4Android Cleaner script to take care of that.
I have tested this on all Nougat ROM available right now and it's working very well. The script will remove MusicFX, AudioFX, SoundFX or DSPManager.
Also in order to make V4A working inside any app, audio_effects.conf and audio_policy.conf needed to be replaced.
In short all you need to do is flash it in TWRP before or after V4A installation.After when you boot up there is no need to update driver anymore.
It's all done, just turn that switch ON in V4A app and enjoy your favorite tunes.
Click to expand...
Click to collapse
HOW TO FIX ViPER4Android NOT INSTALLS DRIVERS!
1. Make sure that you have Busybox intsalled!
You can install it by using this application on the play store https://goo.gl/LztXpM
2. Make sure that you have at least 5mb Free in your system partition!
To check the free space in /system use this app https://goo.gl/D3lcm5 and go to the "advanced" menu
3. After installing busybox, try to reinstall the ViPER4Android drivers and reboot your device!
PS:
I test it on CyanogenMod 14.1 and it works for me.MAKE BACKUP BEFORE YOU TRY ANYITHING.First flash ViPER4Android Cleaner then ViPER4Android_2.5.0.5_guitardedhero.zip
It says v4a could not acquire root permission. I can use root in other apps, not sure what the issue is.
EDIT: I fixed it by rebooting, thanks a lot for this, it works
Yotoprules said:
It says v4a could not acquire root permission. I can use root in other apps, not sure what the issue is.
EDIT: I fixed it by rebooting, thanks a lot for this, it works
Click to expand...
Click to collapse
A lot things in cm 14.1 can be fixed with reboot xD
mefistoreyon said:
A lot things in cm 14.1 can be fixed with reboot xD
Click to expand...
Click to collapse
I'm not using cm14, using fake Nexus ROM on Nexus 5
that's great.but i used magisk for v4a.i am Android 7.1
How can I remove it? The bass quality is terrible for me, on my old ROM it came with AudioFX and that was much better
Yotoprules said:
How can I remove it? The bass quality is terrible for me, on my old ROM it came with AudioFX and that was much better
Click to expand...
Click to collapse
Saddly I don't know.You can restore your backup before installing it, or to turn it off and disable it maybe.
mefistoreyon said:
Saddly I don't know.You can restore your backup before installing it, or to turn it off and disable it maybe.
Click to expand...
Click to collapse
I didn't make a backup. Doesn't the cleaner remove it?
Yotoprules said:
I didn't make a backup. Doesn't the cleaner remove it?
Click to expand...
Click to collapse
Can't say, I can check later but I think is removing only stock stuff.
Send from HTC One M8 running CyanogenMod™ 14.1 by Tapatalk
Strange, viper4android randomly stopped working, settings doing nothing anymore.
Yotoprules said:
Strange, viper4android randomly stopped working, settings doing nothing anymore.
Click to expand...
Click to collapse
Sometimes ,after restart, if I open the app I got "Viper doesn't respond" or something but after 1-2 min its okay.
mefistoreyon said:
Sometimes ,after restart, if I open the app I got "Viper doesn't respond" or something but after 1-2 min its okay.
Click to expand...
Click to collapse
I mean there is no effect on sound anymore.
what does it mean when i keep getting the io erorr even though i granted it storage permission and root?
There is a little noise background when listining some quit slow songs (like interstellar ost) any fix or option advice?
Works great! Best app that ever came out for portable media devices! Zhuang you are god!! Cant thank you enough.
Help me, pls
onionchibi said:
Help me, pls
Click to expand...
Click to collapse
Flash SuperSU
onionchibi said:
Help me, pls
Click to expand...
Click to collapse
download an app called root checker, then download another app called SElinux mode changer and then open it, grant root and set device to permissive. Then close viper4android and restart phone! If this doesn't fix it, wipe cache and dalvik in recovery and then reboot. If that still doesn't work, try downloading Dr.ketan's viper4android fix app on any device from the Google play store. Hope this helps.
it'sup said:
download an app called root checker, then download another app called SElinux mode changer and then open it, grant root and set device to permissive. Then close viper4android and restart phone! If this doesn't fix it, wipe cache and dalvik in recovery and then reboot. If that still doesn't work, try downloading Dr.ketan's viper4android fix app on any device from the Google play store. Hope this helps.
Click to expand...
Click to collapse
u mean this app: https://play.google.com/store/apps/details?id=com.yahoo.dr.ketan.utilitiesn4
And exactly what i must to do?
Got this error.... I m on rr remix , i have root,i guess the problem is the app isnt asking for it...
P.S How i can verify if v4a is working?
Sent from my HTC One M8 using Tapatalk
For Oxygen OS - 5.1.3 Oreo on Oneplus 5T.
Flash in TWRP after making a backup.
Please read all info below.
{
"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"
}
!!! CAUTION !!!
Use at your own risk. Backup before flashing.
I am not responsible for bricked devices,
thermonuclear war or your monkey dancing samba!
IMPORTANT INFO:
Flashing
The installer changes one file. It overwrites \system\etc\permissions\handheld_core_hardware.xml
with an updated version to enable the Google Daydream support.
Removing
There is also the remover ZIP. It restores the stock OOS 5.1.3 permission file.
After flashing - get ready
You wiped your cache and dalvik and boot the device.
Go to your application list and show system apps.
Delete cache and data of the Play Store app so Daydream is
downloadable via Play Store. Open Play Store,
do not forget to set your previous Play Store configuration and install:
• Daydream
• Daydream Keyboard
• Google VR Services
Some reported that setting to skip all intros in Daydream developers options
fixed problems that occured.
Start, set the other config which is needed and try. For me it works fine.
The only thing that is a bit sad is that the 5T with full HD gives a not very sharp display view - it is grainy.
๏[-ิ_•ิ]๏
Does it work on 5.0.3?
Also, does it trigger the 'safetynet'?
lockywolf said:
Does it work on 5.0.3?
Click to expand...
Click to collapse
Actually the file did not change for 5.0.3, but I changed the ZIP filename to clearify.
lockywolf said:
Also, does it trigger the 'safetynet'?
Click to expand...
Click to collapse
I don't think so.
By the way; it is a tiny mod that does no heavy system tweaking.
I made it just for convenience so users do not need to use a root explorer and text editor for the changes.
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
CZ Eddie said:
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
Click to expand...
Click to collapse
This is happening to me as well on AICP. Wanting this to work lol. Please keep me updated if you find anything out!
CZ Eddie said:
Just FYI, it's not working in Oreo Resurrection Remix.
Click to expand...
Click to collapse
bschmidy10 said:
Please keep me updated if you find anything out!
Click to expand...
Click to collapse
See, I am not a real dev... just some guy with basic knowledge. I updated the ZIP and made two new for the ROMs you use.
Try them, but read the OP/CAUTION section please.
The attached ZIPs contain the modified file from your ROMs which are different in one line compared to OOS.
Plus I added a mod for the build.prop to maybe make it work.
If all fails I guess this try was just an interesting waste of time,
and someone more advanced would have to figure out a possible solution.
•••
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
CZ Eddie said:
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
Click to expand...
Click to collapse
As I wrote I can not help any further.
I installed Google VR keyboard, Daydream, VR services etc. and tested some apps under OOS 5.0.3, but all without VR hardware - I do not own the headset/controller. I enabled developer options on Daydream and skipped all intros, read that elsewhere.
I've got the same problem, RR 8.0.1. Logcat implies that the ACore process lacks permissions to access the VR hardware, and crashes upon attempting it, taking the entire systemui and all of its children with it.
I'm in the process of experimenting and seeing if it's possible to grant those permissions somehow..
Anybody got it working? I saw the set today at a store and thought about buying it...
This has always worked for me: https://www.xda-developers.com/force-daydream-vr-compatibility/
never needed to change the device name, just added the 2 lines and rebooted. Daydream apps download and update via playstore as well.
OTA Updates
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
aschi2403 said:
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
Click to expand...
Click to collapse
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
t-ryder said:
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
Click to expand...
Click to collapse
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
aschi2403 said:
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
Click to expand...
Click to collapse
I tried it and I didn't face any of my concerns, but I'm on OxygenOs 5.1.2 and after flashing this, wiping cache, then reboot. Daydream App after a long black screen shows me, that my device isn't compatible with Daydream. Did I do something wrong or is it because of the OxygenOS Version?
EDIT: see post #19
I just bought a Daydream Set (v1) for like 20$ second hand online. Will report regarding further testing when the set has arrived.
Updated for Oxygen OS 5.1.3
Got my headset and all works fine. The image is a bit grainy because 5T has only full HD.
No need for an installer with build.prop changes. I tested the system changes and updated the installer and remover.
If you have tried the old installer/enabler you may restore your build.prop using a root file explorer. It is located in /system (.bak file).
Have fun.
M.Sami said:
never needed to change the device name, just added the 2 lines and rebooted.
Click to expand...
Click to collapse
Yes, you are right.
Original post with samples photos [link]
{
"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"
}
Here are the full photos in this album.
Before using the Google Camera HDR+, you have to enable Camera API 2 in the MIUI, unless any version of Google Camera you install WILL HAVE NO HDR+ EFFECT OR CRASH AFTER OPENING!!!
The way I choose to enable Camera 2 API on MIUI is through the Magisk platform, and there are 4 steps of prerequisites to get to this:
Unlock the bootloader
You need to go to MIUI unlock page and follow the steps to unlock your phone’s Bootloader.
During the process, you will also need to install the driver in computer for your phone.
Flash the 3'rd party recovery, like TWRP
Go to TWRP devices page to download the TWRP recovery for your model, and boot your phone into Fastboot Mode by holding the volume down & power button until it boot into fastboot.
Also download the Android platform tools, unzip, and open CMD on windows or terminal on macOS and cd (move) to your unzip directory.
After that, flash the TWRP recovery into your phone.
Code:
fastboot flash recovery $your_download_recovery.img
Check to flash process is success (you will see the “OK” in the command line), and boot your phone into recovery:
Code:
fastboot boot $your_download_recovery.img
and slide the button to right to enable modification, disable the MIUI’s recovery.
Flash the Magisk platform
Now the custom 3'rd part recovery is completely installed, we can install Magisk now.
Download the magisk from the developer’s XDA page, copy into your phone SD, select and slide to flash the magisk with TWRP install function .
Flash the Camera 2 API enabler
The previous Camera 2 API enabler is decrepit, so I rewrite a newer version that can work with Magisk 15+.
Flash the zip to enable enable Camera 2 API.
You can check whether you successfully enable the Camera 2 API by Camera 2 API probe:
Install Google Camera Port (HDR+) App
Now the prerequisite is complete, we can finally install the Google Camera Port now.
Here is a Port Google Camera collection page, I recommend using MGCamera_5.1.0.18_R4X series which maintain by @Arthur, and here is my recommend settings:
[Reserved]
Are you using China veriant or Indian?
Shahitto said:
Are you using China veriant or Indian?
Click to expand...
Click to collapse
I bought it at Taiwan, it's a China Variant which use Global Android 8.1 MIUI 9.5 ROM
jhangyu said:
I bought it at Taiwan, it's a China Variant which use Global Android 8.1 MIUI 9.5 ROM
Click to expand...
Click to collapse
So it will also work with indian variant? correct?
Also does this method work with Custom oreo ROM?
KuldeepShivankar said:
So it will also work with indian variant? correct?
Also does this method work with Custom oreo ROM?
Click to expand...
Click to collapse
Yes, this magisk trick can work on any xiaomi device announced in 3 years
Can anybody post front camera megapixel screen? In MIUI 10, my phone front camera megapixel is limited to 5mp.
I followed your settings in Latest RR Rom and mine is China variant but front camera HDR in front portrait doesn't work in low light at all. Thanks for sharing
Can you pls upload thecamera2api enabler here?
It doesn't seems to work for me, I have enabled persist.camera.HAL3.enabled=1 but it still run legacy mode
I'm on Xiaomi Redmi Note Pro (china) running xiaomi.eu rom 8.5.10 with magisk 16.4
any suggestions?
krizky82 said:
It doesn't seems to work for me, I have enabled persist.camera.HAL3.enabled=1 but it still run legacy mode
I'm on Xiaomi Redmi Note Pro (china) running xiaomi.eu rom 8.5.10 with magisk 16.4
any suggestions?
Click to expand...
Click to collapse
I have exactly the same issue. It seems to be a Xiaomi.eu related issue.
n3w0rk said:
I have exactly the same issue. It seems to be a Xiaomi.eu related issue.
Click to expand...
Click to collapse
thanks for the confirmation... I guess I'll try it later when MIUI 10 came out, I hope it will be fixed by then.
how do i download the zip from github? is it just the green clone or download? tried it transfered the zip and flashed through twrp, got a error in return
EDIT: got it working by unzipping and rezipping just the files then flashing it.
can the zip be used on Nougat 9.2 version?
krizky82 said:
It doesn't seems to work for me, I have enabled persist.camera.HAL3.enabled=1 but it still run legacy mode
I'm on Xiaomi Redmi Note Pro (china) running xiaomi.eu rom 8.5.10 with magisk 16.4
any suggestions?
Click to expand...
Click to collapse
Please read the article again, I use a MAGISK MODULE to enable camera2 api, not modify the .prop file.
puttytatko said:
Can you pls upload thecamera2api enabler here?
Click to expand...
Click to collapse
No, please just download it from github.
I tried many Magisk module and non of them is working. The Module is executed successfully, but camera2api can't be activated.
The only method for me to active camera2api is to edit the build.prop.
Weird...
I'm using MIUI 9.5.6.0
e_mc_square said:
I tried many Magisk module and non of them is working. The Module is executed successfully, but camera2api can't be activated.
The only method for me to active camera2api is to edit the build.prop.
Weird...
I'm using MIUI 9.5.6.0
Click to expand...
Click to collapse
Same here.
jhangyu said:
Please read the article again, I use a MAGISK MODULE to enable camera2 api, not modify the .prop file.
Click to expand...
Click to collapse
I use magisk too
jon_snowGOT said:
Same here.
Click to expand...
Click to collapse
It happen on global stable rom.
Hello everyone!
I got this device last year and always wanted GSI to run properly in the device. In other guide shows GSI can be properly installed however, it rendered wrong rotation and sound sometimes muffled. I want to get rid ZUI 12/13 because notification problem and suspicious with Chinese rom. With GSI we can have long term device support and security. I am using stock recovery only and stock fastbootd. Root with magisk is sometime hit or miss. I managed to fix with a ported miui vendor img and simple build.prop alteration.
Prepare:
Working device
Unlocked bootloader
Win7/8/10/11 (installed FastBoot driver)
Make sure to be based on the ZUI_13.0.430 version (link attached)
Download GSI J716F script.
Type C dongle to mouse. (needed)
Steps:
1) Restore with Qfil to ZUI_13.0.430 (link attached)
2) Download and extract GSI J716F script.
3) Reboot your device to fastbootd with adb reboot fastboot.
4) Run gsi system flasher for j716f only.exe and press 1. On next screen, press any button. Connect your device until it restore.
5) Do factory reset in recovery mode then reboot.
6) Once system is rebooted. Connect type C dongle with mouse to the device and finish the setup. Please note that rotation and touch is not in sync.
7) Install magisk and make sure proper root. Install build.prop editor. (link attached)
8) Open build.prop and grant superuser access. Add entry ro.surface_flinger.primary_display_orientation at first column and ORIENTATION_270 at second column.
8. Save dan reboot.
9. Everything is working now but bare in mind you need to install some magisk module to get proper sound manager, safetynet fix, AOD support and auto brightness fix from Y700.
What is wroking:
1. Wifi
2. Bluetooth
3. Brightness adjustment (Auto brightness need magisk module)
4. 60Hz/90Hz refresh rate
5. Camera, flashlight and face unlock
6. Working sensors
7. Screen rotation
8. Dual speakers
9. Linear motor
Bug: d2tw and flip screen
Please tell me other bugs
Download : https://drive.google.com/drive/folders/1F4oQflyK6PgfnstJacFOPGaQzZMmJyfQ?usp=sharing
Once root and magisk is properly installed. You can install several magisk module to fix, play store verfication, auto brightness, sound manager and APTX (HD) module for bluetooth.
1) Install each modules.
2) Reboot.
Install these 2 apk to get better camera and proper AOD support
1) Install trebleApp(1).apk
2) Gcam MGC_8.1.101_A9_GV2b_snap.apk
3) You can disable the stock camera app.
In case you want to try other gsi system instead of CrDroid 8.6 prepped. You can simply replace system.img in gsi j716f scipt.zip\gsi j716f scipt\bin\system\system.img.
See the difference.
Reserved
is L1 working?
lordzinh said:
is L1 working?
Click to expand...
Click to collapse
Nope.
Thanks for this...
I hate ZUI, been wanting to try GSI for a while, just didn't want the bugs...
This looks like it's mostly working now .
gunalarix8 said:
lease tell me other bugs
Download : https://drive.google.com/drive/folders/1F4oQflyK6PgfnstJacFOPGaQzZMmJyfQ?usp=sharing
Click to expand...
Click to collapse
Some files on the "3 Tools folder have 0 bytes size" could you reupload them
{
"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"
}
Please remove double post
Awesome work, thanks so much. Hoping to try this soon, how's the battery life been though compared to stock?
eDooM85 said:
Some files on the "3 Tools folder have 0 bytes size" could you reupload themView attachment 5730137
Click to expand...
Click to collapse
sorry for late reply, files has been updated. thank you
gunalarix8 said:
sorry for late reply, files has been updated. thank you
Click to expand...
Click to collapse
Thx I'll try to install a GSI this weekend.
I have been waiting for this, looks like it is mostly working. saw the video too.
thank you for doing this. I will try this because I hate ZUI
gunalarix8 said:
lease tell me other bugs
Click to expand...
Click to collapse
Just installed it, Look good so far just a couple of question:
How did you enable Linux SE?
also how do you customiz/disable this bar?
eDooM85 said:
Just installed it, Look good so far just a couple of question:
How did you enable Linux SE?
View attachment 5736353
also how do you customiz/disable this bar?
View attachment 5736359
Click to expand...
Click to collapse
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
gunalarix8 said:
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
Click to expand...
Click to collapse
the only thing complicated is the setting up part without touch control (my mouse was also detected as a keyboard) and pretty much I had to config without conecting to the internet (couldnt enter my wifi password),
but after the "build.prop" step, everything else is working fine so far
gunalarix8 said:
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
Click to expand...
Click to collapse
Just an update, streaming apps just give errors, I tried Disney+/HBO Max/Paramount only youtube works fine, that's a deal breaker for me , I will try other GSI
eDooM85 said:
Just an update, streaming apps just give errors, I tried Disney+/HBO Max/Paramount only youtube works fine, that's a deal breaker for me , I will try other GSI
Click to expand...
Click to collapse
Isn't that because the widevine level (DRM) is wrong due to the unlocked bootloader?
I think all GSI roms will suffer the same problem... unless someone knows how to fix it with a magisk module or something ... as I they all need an unlocked bootloader..
Other than the DRM issue how does itbrun?
tinybilbo said:
Isn't that because the widevine level (DRM) is wrong due to the unlocked bootloader?
I think all GSI roms will suffer the same problem... unless someone knows how to fix it with a magisk module or something ... as I they all need an unlocked bootloader..
Other than the DRM issue how does itbrun?
Click to expand...
Click to collapse
The problem it's not widevine Lv1 with Lv3 you can view content, the diference is that you can see it only in SD (480p) right now just throws an error loading content for example disney+ show this:
Do you know if OTA updates will work with this method? Or would you have to manually set everything up again.
gunalarix8 said:
With GSI we can have long term device support and security.
Click to expand...
Click to collapse
You say you care about security but you're okay with selinux in permissive mode?
I have just tried this but I'm not convinced this is a secure rom. Theres this chinese app that randomly appeared and dissapeared. It's called com.iflytek.inputmethod and is made by iFlytek, a chinese state owned company which has been sanctioned by the US for spying.
I'm reverting to another GSI without autorotate.
Hi to all my fellow Pixel 6a users. As you know, Google thing is to develop awesome tools and then to only allow a handful of people to use them. But I don't like that, so here's a way to enable Motion Mode, i.e. Action Pan and Long Exposure, and also Audio Zoom on your Pixel 6a. It's pretty simple but I couldn't find any guides online.
Requirements :
- Magisk
- the MagiskHide Props Config module
- a terminal emulator app, Termux is great
Steps :
- Flash the module in Magisk Manager and reboot
- Open your terminal, type "su" and then "props"
- First, change device fingerprint to Pixel 6 : type successively "1", "f", "7", "28" and finally "y". Reboot.
- Once your device restarted, go back to your terminal, type "su" and then "props". Type "3" to go to Device Simulation, and then "2,3,5,10". Nothing else, else your phone may bootloop !
- Reboot and enjoy !
You may need to delete Gcam data.
I did this on my Pixel one week ago and everything still work for me (wide angle, slow motion, safety net...). You still may need to disable everything before updating your phone.
Edit :
As pointed out by sebasgc, the custom Gcam by BigKaka enables Motion Mode on all devices (tried with AGC 8.4.300.18_V_9.3).
It doesn't work for me. I do not see motion mode in the application after applying the modification. Are you using the latest official camera app for this?
That's strange, it works with the lastest stable of the play store on my pixel.
Is "Device simulation" enabled in MagiskHide Props Config ?
Did you try rebooting and erasing Gcam data ?
Yes, I tried rebooting and wipe gcam app data. It's my settings in module
Spoiler
{
"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"
}
Followed your guide, and got it working really easily! Thanks a lot!
I tried this guide again and it started work for me. Idk where I made mistake before. Thank you!
@Papipoulpe Hi, thank you for the work but is not working for me, I made a video.
I'm on build TP1A.221105.002, MVK Kernel, Magisk 25.2, MargiskHide Props Config v6.1.2-v137
EDIT: With stock kernel now working
charly30 said:
@Papipoulpe Hi, thank you for the work but is not working for me, I made a video.
I'm on build TP1A.221105.002, MVK Kernel, Magisk 25.2, MargiskHide Props Config v6.1.2-v137
video
Click to expand...
Click to collapse
It is possible that it is the MVK kernel that is causing the tutorial to not work. The first time (with MVK kernel) it didn't work for me, I made a second attempt already with stock kernel and the tutorial started working. However, this is only my theory. Someone would have to confirm if it works for them on the MVK kernel
Nice, worked for me on the latest beta! Thx
Will this prevent you from taking OTA updates, or will there be other negative side effects from having a Pixel 6 fingerprint on your 6a?
Wont work for me, im on latest december update
Madseb said:
Wont work for me, im on latest december update
Click to expand...
Click to collapse
for me works
charly30 said:
for me works
Click to expand...
Click to collapse
After last step where you have to put the "2,3,5,10"... I got a new window where you have to select 1 for enable, 2 dissable, 3 exit i select enable and the reboot im doing thia correctly?
What option do i have to choose after this i put enable and wont work
Yep, not working for me also on Dec update. Could anyone who got it working share this screen shot?
Madseb said:
Wont work for me, im on latest december update
Click to expand...
Click to collapse
i finally got it working. all i did was add an extra step. but before redoing all those steps, i did reset the props and gcam data once.
Once your device restarted, go back to your terminal, type "su" and then "props". Type "3" to go to Device Simulation, and then "2,3,5,10". Nothing else, else your phone may bootloop !
Click to expand...
Click to collapse
before this step, on the terminal, need to enable the emulation first, which is "s" and enter. and after this just follow the step on the terminal and reboot. open camera apps, and there is motion mode. yay
koax88 said:
i finally got it working. all i did was add an extra step. but before redoing all those steps, i did reset the props and gcam data once.
before this step, on the terminal, need to enable the emulation first, which is "s" and enter. and after this just follow the step on the terminal and reboot. open camera apps, and there is motion mode. yay
Click to expand...
Click to collapse
Now is working, thanks mate!
sadly, i found a bug, potrait mode, at 1x is not working. 2x and front face is working. and i did noticed the processing took a bit longger than usual.
edited : well,potrait mode is still working at 1.1x , not much different, i can live with it.
Hi,
Can you please share a screenshot of the stock Gcam app where this option (Motion Mode) appears?
Is it the same things as "Cinematic Pan" ??
UPDATE: I got it working now, it is a different option that appears below the shutter button! Thanks for sharing!!
You can install BigKaka's gcam too, i got it working on that way.