Related
GLOBAL USERS, LATEST NEWS: WORKING GCAM3 with FRONT CAM and TIME LAPSE!
This thread was created to achieve, at first, two goals:
Organize useful information on the main topic about GCAM for GL/CN users and CONSTANTLY UPDATE IT;
Direct new users to a "solution" regarding GCAM on Global/China variants;
MY SPECS:
Phone: Redmi Note 5 Pro 64GB/4GB (CN and came with GLOBAL ROM installed)
ROM: Havoc Mod ROM (Android 9.0/Pie)
Understand the "problem" between the Indian vs Global/CN variants:
Indian variant uses Sony sensors on both front and rear cameras. So modders didn't had too much trouble porting GCAM for them;
GLOBAL/CN variants have the Samsung S5K2L7 sensor (same sensor used in RN6 Pro) on the rear, and on the front camera we have a Omnivision sensor (here lies the problem).
Know that: THERE'S NO WAY OF MAKING GCAM WORK ON ANDROID PIE WITHOUT A PATCH!
MAGISK METHOD NOTE:
UPDATE: There might be a light for your, warrior!
As gracefully explained by our fellow Desmanto, there are some steps you can take in order to make the Magisk modules work.
If it helps you on your lonely journey, please hit the Thanks button on his response. I'll only link his explanation.
I noticed that installing a PATCH through it isn't a guarantee of success.
Even when I installed AdAway on my phone, magisk took a while to finally grant root access to it... So it means it's a shot in the dark.
Once I was able to install the RN5 Camera Patch v1.035a(Pie 9.0).zip by nhappyman and make it properly work. But only once!
As pointed out by the user misiek735:
"If you install everything and you choose 4k with eis enabled in gcam 5.1 settings
and it does not work (camera error) then it means that patch is not working
at all and you make somewhere during the instalation proces a mistake."Since the process of installing the patch, rebooting, checking if the patch was installed successfully, removing it, rebooting, installing again...
isn't as pretty as I'd like, I advise you all to take the TWRP route.
TWRP ROUTE: THE LIGHT AT THE END OF THE ROAD:
Right, this is where the fun begins!
First of all, my rig consists of two GCAM:
Pixel 3 (For anything related to rear camera: Normal, Portrait, Nightsight and SlowMo) - MGC_6.1.021_BSG_Arnova-based_v.1.3d_TInNeun_2
Pixel 2 (Front Camera; Front Portrait Mode) - GoogleCamera-5.1.018.177624777-Urnyx05Mod
Patch used: RN5 Camera Patch TWRP v1.035a (Pie_9.0).zip (Reading through threads, I've came to the conclusion this one is guaranteed to work. New versions are out there to be tested. Please share your results)
With these guys I can do pretty everything* (passing the "misiek735 test" pointed out earlier):
SlowMo: [email protected] or [email protected]
Front/Rear Camera Portrait
Front/Rear Live Motion
Rear Camera video: [email protected], [email protected]
>>>*REMEMBER THAT ANY PIXEL 3 CAMERA FCs ON FRONT CAMERA!<<<
>>>*Not anymore. Check the end of this post!<<<
DOWNLOAD:
- Fantastic mods/patch, but... Where to find them?
At the moment, I'm going to point out the direction (since I'm not aware if I hold any rights to upload myself those files)
TWRP v1.035a patch:
Look for a Telegram Group called RN5 Camera Patch™ | Channel (@rn5cp - https://t.me/rn5cp)
Go to group details (tap on the group's title) -> Files -> Search in October 2018 for: RN5 Camera Patch TWRP v1.035a (Pie 9.0).zip
GCAMs:
Celso Azevedo's Page;
Telegram Group: Google Camera (Whyred) ( @gcamWhyred )
Telegram Group: Gcams Downloads (Whyred) ( @gcamdownloadswhyred )
And this very XDA page.
It's worth reading this message posted by Desmanto
Hope this thread can provide useful and reliable information for you guys.
Please share additional information, ask questions and correct any wrong information.
Cheers.
UPDATE: 2019/04/30
LATEST NEWS: WE HAVE A WORKING GCAM3!
Yesterday was release a brand new version for us GLOBAL users! It's a GCAM3 (Pixel 3 Camera App) with a working front camera!
Search for the APK on the Telegram Group gcamWhyred!
Look for:
Gcam 6.2.024 Advanced V2.1.beta._190429.1903.apk
In order to make the front camera work and use a lag-free app, you must use these settings presented on the attachments!
Or click here and check my shared Google Photos gallery.
Note:
I'm currently using the TWRP v1.035a patch
There's a new version called RN5 Camera Patch v2.034a that might fix the issues I'm going to talk about next, but I didn't test it yet (please, you can provide feedback here if you will), so bear with me.
Known Issues (So far):
If you zoom (use the digital zoom prior to the shot), it'll FC the app and a low resolution (probably the image in the buffer) will be saved in your gallery. (Zoomed shots on the front camera work!) Just set "Using Sabre" OFF and will be good to go! (From what I've understood this an algorithm to enhance zoomed pictures)
Occurred to me once, but you might get an black picture every now and never.
While recording something the "viewfinder" might show a worst image than the one which is actually being recorded.
Night Sight is laggy! It'll work as intended but you'll experience it's 1/3s shutter speed. Seems like it's already collecting data about the scenario prior to the shot.
UPDATE: 2019/05/14
Latest News: We have a working GCAM v6.2.030 (i.e. Time Lapse capable)
Today was shared on gcamWhyred telegram group a GCAM3 with the new time lapse.
Look for:
Gcam_6.2.030_Advanced_V2.1beta6.190512.1059.apk - Link for those who avoids Telegram (not posted by me)
In order to make the front camera work and use a lag-free app, you must:
Enable advanced mode.
Use these settings for the front camera and disable Sabre (also use RAW10 on RAW format, if I'm not wrong this will remove the lag on the rear camera).
The "Disabled Google Photo" actually sets it as default gallery (probably a bug)
In advanced settings, if you try to use the dark theme, it won't work. (Again, there's a reason why it still called "beta")
Created: 2019/03/06
Last Updated: 2019/05/14
Can you link here or dm me newest patch version for Pie ? @SpiderPack
I would like magisk version
EDIT: v2.025a patch for you
Both Miui and Pie 9.0 Custom
Only Magisk because there isn't TWRP edition of this version
https://mega.nz/#F!vDRVVC6b!M3RMVNkUK-RoEpt-IkwU_A
Gcam which I am using now:
https://www.celsoazevedo.com/files/...f/GCam-5.1.018-Pixel2Mod-Arnova8G2-V8.3b1.apk
Please recommend good gcam so i also stick it there
Has anyone tried this on the latest stable MIUI 10 build?
And I can see v2.025a Patch Module in the Telegram group. What's that for?
SpiderPack said:
GLOBAL/CN variants have the same Sony sensor on the rear, but on the front camera we have a Omnivision sensor (here lies the problem).
Click to expand...
Click to collapse
A small correction here. The Global/CN variant (RN5 AI) doesn't have Sony IMX486 sensor on the rear camera. Instead, it sports Samsung S5K2L7 sensor (same sensor used in RN6 Pro) with effective pixel size of 1.4 μm.
The4anoni said:
Can you link here or dm me newest patch version for Pie ? @SpiderPack
I would like magisk version
Click to expand...
Click to collapse
You can find them on RN5 Camera Patch™ | Channel telegram group.
SpiderPack said:
You can find them on RN5 Camera Patch™ | Channel telegram group.
Click to expand...
Click to collapse
I don't have telegram....
Thank you for the amazing thread, I'm sure it'll help a lot of people! But you're missing something: you should give the groups' @ instead of the groups' name. With the name only it's a lot harder to find.
TheForgotten said:
Thank you for the amazing thread, I'm sure it'll help a lot of people! But you're missing something: you should give the groups' @ instead of the groups' name. With the name only it's a lot harder to find.
Click to expand...
Click to collapse
Thanks for your input! I'll add the links.
great thread, thanks for sharing, I have one question though, how to undo a TWRP patch? is there a way like we have in Magisk? thanks in advance
Hello,
Is there any way to fix whatsapp video call lag when camera2api / patch is enabled? Everything in gcam 5.1 working fine with the patch, but the lags at whatsapp video call is a deal breaker for me, hope there is a way, been looking at how to fix this since day one..
Cheers!
*Im using PE 9.0
Hacksfallout said:
Hello,
Is there any way to fix whatsapp video call lag when camera2api / patch is enabled? Everything in gcam 5.1 working fine with the patch, but the lags at whatsapp video call is a deal breaker for me, hope there is a way, been looking at how to fix this since day one..
Cheers!
*Im using PE 9.0
Click to expand...
Click to collapse
Hm... That's odd, I've just tested with my boss and the WhatsApp Video Call was good enough. I don't know if it was supposed to have less delay (though, to me, was acceptable), but unfortunately I'm not aware of any fixes.
Dr.TheMaster said:
great thread, thanks for sharing, I have one question though, how to undo a TWRP patch? is there a way like we have in Magisk? thanks in advance
Click to expand...
Click to collapse
Yes! I'm pretty sure that dirty flashing the same ROM (and version) will bring everything back to what it was.
Best Gcam for v2.025a patch and 9.0 Resurrection Remix ?
Also uploading v2.025a Magisk (no TWRP Version) patch for MIUI 10 and Pie 9.0 Custom
Here
https://forum.xda-developers.com/showpost.php?p=79054168&postcount=2
i've tried every patch, every gcam version, none worked. crashes, only blue pictures, pictures not taken at all. As much as I love whyred, gcam ports are mehh
KissKK said:
i've tried every patch, every gcam version, none worked. crashes, only blue pictures, pictures not taken at all. As much as I love whyred, gcam ports are mehh
Click to expand...
Click to collapse
Really? Please share your specs* and maybe we can find something for you
*I meant the ROM you're using.
SpiderPack said:
Hm... That's odd, I've just tested with my boss and the WhatsApp Video Call was good enough. I don't know if it was supposed to have less delay (though, to me, was acceptable), but unfortunately I'm not aware of any fixes.
Yes! I'm pretty sure that dirty flashing the same ROM (and version) will bring everything back to what it was.
Click to expand...
Click to collapse
Hmm thats weird, are you in Pixel Experience rom? Because i only facing this issue in PE, at Havoc 2.2 and MIUI the bug does not happen
KissKK said:
i've tried every patch, every gcam version, none worked. crashes, only blue pictures, pictures not taken at all. As much as I love whyred, gcam ports are mehh
Click to expand...
Click to collapse
Try this bro
https://forum.xda-developers.com/showpost.php?p=79054168&postcount=2
Make sure to remove previous patches, etc. or best is reflash rom
Works like a charm on Resurrection Remix Pie
I am using 06.03.2019 build
Works on AOISP 9.0
Hacksfallout said:
Hmm thats weird, are you in Pixel Experience rom? Because i only facing this issue in PE, at Havoc 2.2 and MIUI the bug does not happen
Click to expand...
Click to collapse
No, I'm on Havoc OS Mod.
Is PE camera2api enabled by default? Check with the developer? Maybe?
Let me ask you something else: Why did you end up on PE? I went through the RN5 forum before buying my phone, and even though PE looked fancy and awesome, HavocOS seemed to provide more customization.
SpiderPack said:
No, I'm on Havoc OS Mod.
Is PE camera2api enabled by default? Check with the developer? Maybe?
Let me ask you something else: Why did you end up on PE? I went through the RN5 forum before buying my phone, and even though PE looked fancy and awesome, HavocOS seemed to provide more customization.
Click to expand...
Click to collapse
Oh i see now why at havoc the whatsapp bug does not occur, i looked at their changelog, one line caught my eye.. its the "Force HAL1 package in some app", i think that may be the case, the devs of Havoc is aware of this bug i think, so whatsapp must be one of the app that being forced to use HAL1. (HAL3 is camera2api right?)
Hmmm, its more like personal taste i think I kinda like a minimal rom with minimal costumization.. and PE is the one for me, it really gives me the taste of Pixel phone :laugh:
Have anyone tried a TWRP patch newer than version 1.035a?
If so, what's new? Any changelogs?
in this tread, i want to collect first user impressions and/or recognized bugs of miui v.12 on a POCO F2 Pro/Redmi K30 Pro, so please get involved! If you find something else or you have a solution to fix my faults, please explain it.
first of all:
At this time, I think this update is only a collection of optically refreshments together with a newer security patch. (jun.2020) After updating, my system runs flawless and smooth. But what i have recognized in EU (Poco F2) version of rom:
* in the new MIUI v12 the sync tile seems to be removed.
* the visible app symbols in notification bar seems to be reduced up to 3 apps!
will other versions of MIUI v12 have the same behavior or is this to find in QJKEUXM version only?
edit: changed my question
Icetea said:
in this tread, i want to collect first user impressions and/or recognized bugs of miui v.12 (EU rom) on a POCO F2 Pro, so please get involved!
If you find something else or a solution to fix, explain it.
what i have recognized:
At this time, it seems to be only a collection of optically refreshments together with a newer security patch. (jun.2020)
at the moment,it runs flawless and smooth.
but...
* in the new MIUI v12 the sync tile seems to be removed.
* the visible app symbols in notification bar seems to be reduced up to 3 apps!
Click to expand...
Click to collapse
OMG here we go again.
We have a dedicated thread for the EEA version so please stop the cluttering.
https://forum.xda-developers.com/poco-f2-pro/how-to/poco-f2-pro-global-eea-qjkeuxm-t4122357
it is not necessary to use my full post to give a comment about it.?
Hi, I have a problem.
I can play netflix and others apps but
I can not send Netflix/Amazon/HBO/Disney+ etc to my TV.
Widevine l1 updated certificate on footprint, payment methods. Old trick of the pocophone f1.
Screen mirroring ok with my photos/videos ,YouTube and gaming.
With other mobiles, I can do It.
Where is the problem?
I tried miui 12 official EU,. Chinese and beta and android 11 beta 1.
All ROMs failed with this.
Bug in battery stats, no uptime showing on me. numbers too big.
Hi fellas,
I recently bought a Xiaomi Redmi Note 9S, and aside from the fact that it's still running Android 10 over MIUI 12.0.3.0 (Global / EU since I'm in France) when everybody else and their cousin seems to have switched to Android 11 already, everything's peachy with the phone.
My question is borne more out of curiosity than necessity: How better would my photos be if I installed Gcam (Google Camera), rather than keep on using OpenCamera or the Xiaomi app the phone ships with? Would I really see an improvement in the way the Gcam software treats images?
If you think I'd get to gain from the install, then a second question comes to mind: How to install the config file that comes with most of the builds I've found here and there? Last time I installed Gcam on the phone, the config file came separately, and however hard I tried to follow instructions, I never managed to load the config file, so I ditched the app altogether. Patient, I am not for that kind of thing, I'll confess.
So, what gives?
UglyStuff said:
Hi fellas,
I recently bought a Xiaomi Redmi Note 9S, and aside from the fact that it's still running Android 10 over MIUI 12.0.3.0 (Global / EU since I'm in France) when everybody else and their cousin seems to have switched to Android 11 already, everything's peachy with the phone.
My question is borne more out of curiosity than necessity: How better would my photos be if I installed Gcam (Google Camera), rather than keep on using OpenCamera or the Xiaomi app the phone ships with? Would I really see an improvement in the way the Gcam software treats images?
If you think I'd get to gain from the install, then a second question comes to mind: How to install the config file that comes with most of the builds I've found here and there? Last time I installed Gcam on the phone, the config file came separately, and however hard I tried to follow instructions, I never managed to load the config file, so I ditched the app altogether. Patient, I am not for that kind of thing, I'll confess.
So, what gives?
Click to expand...
Click to collapse
gcam use some algorithm to enhance photos to high dynamic range (HDR). you may get better image if you use proper gcam made for your phone.
secondly, config file can be loaded in settings of most gcam. you can use youtube or any tutorial to see how to load configs.
Thanks for your reply, Bhanu. It was my understanding that what Gcam does, mostly, is to apply some sort of software "magic" to what the sensors record, and in this respect, the 48MP main sensor on the Note 9S isn't too shabby, so I'd really like to give it a try, but as I said in my OP, every time I did what was advised in the tutorials I read, i.e. press somewhere in the camera interface (left of the capture button), I always got the same "no config file to load" message, although I had a config file waiting to be installed, one that I had downloaded along with the Gcam .apk file, so I was wondering if there were APKs that already contained said config file, and if so, where can I find them?
For example, this article points at two different builds based on Gcam 8, but it doesn't mention where to find the config file that goes with either one of them.
hi, i like the way you replied,
about gcam i have found v7.4 its recommended to use v7 because they are relatively stable.
link:- http://www.mediafire.com/file/n6zvk...wFjJ1hSydvsFIulyLOShEyHF73I-Hcbch7knXmuWUwVis
just open app and go to settings and developer settings and disable use google photo to use it.
or simply install google photos to make this version work.
Moving away from main thread to avoid spam
Original Question:
Hi,
first of all, thanks a lot for your effort bringing lineage to the pixel 4a.
I've got a problem with the main (front 12.2 MP) camera (please see attached logcat).
When opening the default camera app (as well as with my test with google camera) the screen stays black and I can't take pictures. I'm on build number lineage_sunfish-userdebug 11 RQ2A.210505.003 b609c3a431, but had this problem with the previous build as well (I was able to take pictures a few builds back, though).
Does anyone else have issues with the camera not working or is it just me?
Thanks a lot and let me know, if there's any further info I can provide that would be helpful for troubleshooting.
Thanks and regards,
C
second log from main thread
Original text:
Hey again
I clean installed the 20210527 build (and corresponding recovery) today and first thing I did was trying the camera... The org.lineage.snap is slow to non-responsive, the screen stays black and ultimately the camera app crashes...
The attached log shows multiple errors (as far as a noob like me can tell ).
If I'm the only person affected by this, is there anyone who could help me troubleshoot the issue... different hardware in Europe... or hardware failure... false stock firmware (though 100% sure it was on 11).
Thanks again and regards,
C
(If there's a better place for bug reports, kindly let me know )
reply to post
Hey @mangokm40
thanks for your feedback. I neither have magisk nor any custom kernel installed.
I basically came from stock android 11 and followed the installation instructions .
As per this lineage wiki I installed mindthegapps according to the instructions.
Do you or anybody have any other idea? As I seem to be the only one affected, I guess a bug report wouldn't be in order, would it
Thanks again, appreciate your support
Chris, stop using the stock/default app and use a Gcam port: https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Like PXMod (cstark's PXv4.5: PXv4.5_GoogleCamera_7.2.014.apk (cstark27, 2020-09-04, pixel)
I think you'll find the same and more features than the stock app, and it's a lot more stable. No issues taking front camera pics (you can also enable HDR+ for the front camera).
sk8223 said:
Chris, stop using the stock/default app and use a Gcam port: https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Like PXMod (cstark's PXv4.5: PXv4.5_GoogleCamera_7.2.014.apk (cstark27, 2020-09-04, pixel)
I think you'll find the same and more features than the stock app, and it's a lot more stable. No issues taking front camera pics (you can also enable HDR+ for the front camera).
Click to expand...
Click to collapse
thanks for the input, but i fear, that won't help in my case... I already tried the gcam mod of this post, which didn't work either
there might be darker forces at work with my pixel 4a...
nonetheless, I'll try your version asap and come back with the result.
thanks for your time and effort
I have the same issue. The rear cam stopped working. Upgrading to the latest 18.1 build did not help. I guess an update for "carrier services and device personalization apps" from play is causing this, as this are the only changes i noticed on my p4a.
hey guys,
sorry for the delay, but finally closing the loop on this one.
thanks to @razorloves , who looked a the logs and confirmed my suspicion, that an actual hardware issue might be the issue, I rolled back to stock and was able to confirm, that the camera issue had nothing to do with LOS 18.1 .
the same problem occured with stock, so I returned and exchanged the phone.
new phone with official LOS 18.1 has been working smoothly for two weeks now, including both cameras
so again, thanks @razorloves for your support and of course thanks @PeterCxy for a great rom.
cheers,
C
So I know we're still in the early stages of this device. But I just wanted to get a thread going for V4A on our device.
For those who came from the 6 Pro like I did, you're probably already aware of this, but for those who did not here's the current situation:
V4A was working fine on Android 12 but when Android 13 came around there were some issues. For most phones they got ironed out and at this point I think basically every other phone on A13 has V4A working EXCEPT for the Pixel 6/6 pro. I tried installing V4A myself on my 7 pro to no avail. I don't know much about the details of why it's not working or what's going on "underneath the hood" so to speak but I can only assume that whatever it is that's causing V4A to not work on my 7 pro is at least somewhat similar to the reason it doesn't work on the 6 pro. There are a few people trying to figure out the issue in a thread over in the 6 pro section on XDA which I will link here if you want to stay more up to date about what's going on:
https://forum.xda-developers.com/t/anyone-get-viper4android-worked-on-a13.4480467/
As a side note, I did manage to get JamesDSP to work on my 7 pro, which is an okay alternative for the time being. Not exactly the same but it's better than nothing for sure. The main thing I don't like about it is that it doesn't auto switch profiles when you change between audio devices of the same type, for example switching from bluetooth earbuds to bluetooth car speakers.
I use wavelet and it works really well. Always had trouble getting v4a working
Have you tried Viper Android Repackaged?
I just got my device late yesterday, so I haven't bothered rooting just yet, but it's in my plans. There's usually a certain install method to get it working coming from my older devices, but you can try this as well.
GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.
A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.
github.com
The difficulty is now with the Pixel 7 using a different and exclusive cpu architecture, as viper can't even now even attempt to install the driver.
I've reached out to the dev of that one to see what he says....
Update: they got back to me and said as they can't obtain the source code it can't be recompiled to x64.
I see some 'change petition' from 3 years ago asking for it to be updated to x64 but still nothing, and that was years ago.
Ain't looking good for viper on our new pixels by looks of it...
+1 for wavelet. just paid for the full version and the bass booster is prettyy f**king good.
kinda worth the 8CAD$ not to have to deal with Viper issues all the time or everytime the system OS changes.
I found the following program that may be helpful:
Introduction — LIEF Documentation
lief-project.github.io
Maybe it can be used to convert libv4a_fx.so header from 32-bit into a 64-bit library.
sarabraj.singh said:
+1 for wavelet. just paid for the full version and the bass booster is prettyy f**king good.
kinda worth the 8CAD$ not to have to deal with Viper issues all the time or everytime the system OS changes.
Click to expand...
Click to collapse
Does wavelet work at a root level? Any additional battery drain using it, or does it work as well as viper?
Really doubt V4A will ever work again, the project has been abandoned for years.
People try to "patch" it instead, as there has been no real update.
Also the pixel 7 use 64bit only app and drivers, V4A was never updated to use 64bit drivers.
kdrag0n (look on github) has been working on a POC called PhantomAmp to use rootless audio DSP effects.
The app is for patreon sub only for now.
It's in early stage and only a POC so maybe at some point this could be used.
Deadmau-five said:
I use wavelet and it works really well. Always had trouble getting v4a working
Click to expand...
Click to collapse
I honestly always assumed that EQ apps from the google play store were never as good a something like V4A, but I gave Wavelet a shot and I'm really liking it so far. I like that it automatically switches your settings based on what is connected to your phone, a feature I missed from V4A and that was lacking in JamesDSP. I also like that you don't necessarily need to have a persistent notification, it at least gives you the option to swipe it away. Thanks for bringing this to light (can't believe I didn't know about this for so long lol), will be using this now as it seems like a pretty viable alternative to V4A. It's made by the same guy so it's actually quite similar. Will miss spectrum extension and ViPER clarity though.
Dolby Atmos works with some success. The issue is that it will take a few reboots to get your pin/pattern working on your lockscreen.
Be sure to enable USB debugging in case you need to disable the magisk modules if you get locked out (adb shell magisk --disable-modules)
https://www.pling.com/p/1908400
RJR
cd993 said:
Does wavelet work at a root level? Any additional battery drain using it, or does it work as well as viper?
Click to expand...
Click to collapse
+1 on your battery drain question.
It works without root. I don't see battery drain. Doesn't show up on Accu Battery
Deadmau-five said:
I use wavelet and it works really well. Always had trouble getting v4a working
Click to expand...
Click to collapse
As a long time Viper user, thanks for posting this, it's always a little puzzling to me how audio is a distant priority for Google and how much better it sounds with a little external assistance using the same hardware.
Can't lie, I miss the phones (Samsung?) that let you fine tune both left and right output by playing tones and you indicating if you heard them or not and it adjusting each channel specifically to your abilities to hear each frequency band. As someone with unequal hearing damage this really makes audio better on those phones that provide it.
A possible light at the end of the tunnel is this project, they are aiming to reverse engineer Viper and modernise the files (hopefully that means using x64!). We'll just have to monitor the progress....
GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX
Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.
github.com
Deadmau-five said:
It works without root. I don't see battery drain. Doesn't show up on Accu Battery
Click to expand...
Click to collapse
Battery Guru here and after only a few mins usage, it's showing up. Not that it's a bad thing of course! Will monitor and see how it goes...
cd993 said:
A possible light at the end of the tunnel is this project, they are aiming to reverse engineer Viper and modernise the files (hopefully that means using x64!). We'll just have to monitor the progress....
GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX
Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
This is amazing news!
I'll gladly test it out for you as I've a keen interest in having this working once again! Feel free to send me a message with any contact details, (email or telegram perhaps) if you like and we'll go from there
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
I'll gladly test it out also!!!!
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
Legend!
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
Id like to help test also!