{
"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"
}
MACsposedHistorically, setting a custom MAC address on Android was very easy for rooted users. Starting with Android 12, however, Google's implementation of MAC address randomization has made it impossible, as the MAC address is always changed when the network state is altered. If you have encountered this problem, then you need MACsposed! MACsposed is an Xposed module that blocks the MAC address randomizer on Android 12 and 13 and allows you to once again make use of your favorite tools for setting your MAC address. Simply install MACsposed, enable it, and go back to randomizing your MAC address using your favorite tools for doing so!
WARNING: MACsposed is intended for rooted devices running Android 12 or 13 and requires Xposed. The recommended Xposed variant to use is LSPosed. Other Xposed variants may work, but have not been tested. Additionally, this module cannot be guaranteed to work on all devices. In the worst case, it can cause a bootloop. Use at your own risk.
To use MACsposed:
Install LSposed. This requires your device to be rooted with Magisk. Installation instructions for LSPosed are available here.
Install MACsposed.
Activate the MACsposed module in the LSposed user interface.
Reboot your device and sign in.
Open the quick settings panel. The MACsposed tile will appear.
Toggle the MACsposed tile on or off to enable or disable it.
Use your favorite tool for setting a custom MAC address!
MACsposed is now open source on GitHub! - https://github.com/DavidBerdik/MACsposed
Reserved.
Reserved.
Does this work on Android 10?
I owned a Xiaomi Redmi 9 running Android 10
Ace_Cole said:
Does this work on Android 10?
I owned a Xiaomi Redmi 9 running Android 10
Click to expand...
Click to collapse
The changes that Google made to prevent setting custom MAC addresses from working were only introduced with Android 12, so this app is actually not necessary if you are on Android 10.
Is it working with the last version of Lineageos?
m3m0rx said:
Is it working with the last version of Lineageos?
Click to expand...
Click to collapse
I have not tested this app on LineageOS 19, so I cannot say for sure that it will work, but since LineageOS 19 is based on Android 12, I believe that it probably will work. If you decide to try it, please let me know what your experience is like!
David B. said:
I have not tested this app on LineageOS 19, so I cannot say for sure that it will work, but since LineageOS 19 is based on Android 12, I believe that it probably will work. If you decide to try it, please let me know what your experience is like!
Click to expand...
Click to collapse
I am happy to let you know that I am writtimg on a changed MAC. It is working on Lineage 19-20220720-NIGHTLY-beyond2lte, G975F. The thing is that I had to switch to the Mac app I saw in your pictures, mine did not work.
m3m0rx said:
I am happy to let you know that I am writtimg on a changed MAC. It is working on Lineage 19-20220720-NIGHTLY-beyond2lte, G975F. The thing is that I had to switch to the Mac app I saw in your pictures, mine did not work.
Click to expand...
Click to collapse
That's great! I'm happy to hear that! Thank you for letting me know.
As for the app you used for changing the MAC address, I have found from my own experimenting that many of the MAC address changer apps that are available out there tend to be rather hit-or-miss in terms of how well they operate. Some of them were built for older versions of Android and haven't been updated in a really long time, and so, they were broken even before Android 12. Either way, I'm very happy to hear that it works for you!
MACsposed v1.1.0 with support for Android 13 is now available to download on GitHub. As of this posting, the update is still pending approval on the Google Play Store.
Hello! Can I tweak the module to run on Android 11? Tired of fighting! Wi-Fi is disabled in the settings and disabled in the developer menu. But the dastardly Techno Spark 7 still plays with the MAC.
AndryK111 said:
Hello! Can I tweak the module to run on Android 11? Tired of fighting! Wi-Fi is disabled in the settings and disabled in the developer menu. But the dastardly Techno Spark 7 still plays with the MAC.
Click to expand...
Click to collapse
Certainly! If you get it working, please consider submitting a pull request so I can expand the range of supported devices.
I should warn you that if your phone OEM has tweaked the Android code enough to randomize MAC addresses, it may not be easy to implement the change, as they've likely deviated from AOSP.
The current version just didn't start.
AndryK111 said:
The current version just didn't start.
Click to expand...
Click to collapse
Well the current version is only intended for Android 12 and 13, so I'm not surprised to hear that. If you're lucky, you may be able to get it working by just dropping the minimum SDK version, but honestly, I doubt it. Might be worth trying though.
I do not know how to do it.
offtopic ..... can some read-only file be marked?
AndryK111 said:
I do not know how to do it.
Click to expand...
Click to collapse
Do what? Modify the code?
AndryK111 said:
offtopic ..... can some read-only file be marked?
Click to expand...
Click to collapse
I don't understand the question.
David B. said:
Do what? Modify the code?
I don't understand the question.
Click to expand...
Click to collapse
David B. said:
If you're lucky, you may be able to get it working by just dropping the minimum SDK version
Click to expand...
Click to collapse
I don't know how to reset the minimum version of sdk
AndryK111 said:
I don't know how to reset the minimum version of sdk
Click to expand...
Click to collapse
Oh that's actually pretty easy to do!
Change minSdk 31 to minSdk 30 here: https://github.com/DavidBerdik/MACsposed/blob/master/app/build.gradle#L11
David B. said:
Oh that's actually pretty easy to do!
Change minSdk 31 to minSdk 30 here: https://github.com/DavidBerdik/MACsposed/blob/master/app/build.gradle#L11
Click to expand...
Click to collapse
go to https://github.com/DavidBerdik/MACsposed
"code" => Download ZIP => edit file => what's next? just rename Zip to APK?
Related
TD Fuzzer
This is a simple Xposed module designed to help those that utilize Nitrodesk's Touchdown to connect to their Exchange Activesync systems. Some EAS implementations prohibit certain device types/models from connecting, or if you'd rather present an alternate device when provisioning, this module can help with that. Keep in mind, if your IT staff/Info Security Office discover that you're circumventing their security controls and/or policies, I can't be held accountable if you get reprimanded and/or fired. This module won't circumvent specific policy requirements, such as device or sdcard encryption, strong password requirements, or disabled feature sets (disable IR, disable BT, etc). All it does is replace device-specific information that is collected during device provisioning, and also during each Activesync session (User-Agent header).
A picture is worth a thousand words, or so the saying goes:
{
"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"
}
The device on the top is my HTC One (m7) running Touchdown 8.4.00082 on KK 4.4.2, and the one beneath it is an actual iPhone 5s. The only discernible difference is the Device ID (which can't easily be changed in TD without breaking stuff).
This module should work on most devices running most ROMs. It only hooks the Touchdown package, and has been tested on TD 8.1.x, 8.4.x, and the latest 8.5.00086 against Exchange 2010 SP1 (Activesync v14.1) and Office 365 (Exchange 2013).
Install/Configuration
Install Xposed Framework
Activate Xposed app_process
Install this module and enable in Xposed Installer
Open TD Fuzzer settings and configure options
Reboot or soft-reset
Open Touchdown and provision device (or if already provisioned, go to TD Settings, Connection, ActiveSync button, Refresh ActiveSync Settings)
Source
You can find it on my github
Alternate Install
Also available in the xposed repo
@cities516 can you add to your module index?
Until I get around to adding some device presets into the module, here are some examples straight out of OWA:
iPhone 4S
Phone friendly name: Black iPhone 4S
Device Model: iPhone4C1
Phone OS: iOS 7.0.4 11B554a
Device Operating System Language: en
User agent: Apple-iPhone4C1/1102.55400001
SAMSUNG SGH-I747 (AT&T GS3)
Phone friendly name: d2uc
Device Model: SAMSUNG-SGH-I747
Phone OS: Android
Device Operating System Language: English
User agent: SAMSUNG-SGH-I747/101.403
SAMSUNG SGH-I317 (AT&T GN2)
Phone friendly name: t0lteatt
Device Model: SAMSUNG-SGH-I317
Phone OS: Android
Device Operating System Language: English
User agent: SAMSUNG-SGH-I317/100.40102
Great Work!
I've been search for a solution for this for ages and must I say that your xposed module is by far the only and most effective solution. Big congrats and very much obliged, man.
Because without this, although Touchdown can spoof a device name, the OS, protocols during the Activesync provisioning process will still be "Android 4.4.x" and "Touchdown x.x.x". So from the admin's side, it is still able to identify the spoofing by looking at the OWA mobile log.
Three questions:
1. How does it work? Modifying provisioning communication packets between Touchdown and ActiveSync server? I'm asking this because I want to know if future versions of Touchdown can be supported.
2. Will you consider supporting Android 5.0?
3. Will you consider supporting AOSP email apps, (preferably the apks with Exchange Security byPass working for 4.4.4 and 5.0)
Again, many thanks to you for the great work!:laugh:
XDAAdvocate said:
1. How does it work? Modifying provisioning communication packets between Touchdown and ActiveSync server? I'm asking this because I want to know if future versions of Touchdown can be supported.
Click to expand...
Click to collapse
I've replaced the writeDeviceInfo() method, which builds the provisioning XML object (com.nitrodesk.wbxml.WBXMLSerializer object, to be precise). This should be compatible with any version of TD; it's more specific to the Activesync protocol version (14.1 in this case). If MS changes how devices send provisioning data, then it would have to be updated. Also, there's information that's passed to EAS in the User-Agent header, which this module replaces.
2. Will you consider supporting Android 5.0?
Click to expand...
Click to collapse
Sure, once I have a device running Android L and the Xposed Framework.
3. Will you consider supporting AOSP email apps, (preferably the apks with Exchange Security byPass working for 4.4.4 and 5.0)
Click to expand...
Click to collapse
I've run across at least one xposed module out there that bypasses the AOSP email security restrictions for EAS. Since I don't normally run AOSP roms, it's much harder for me to do any sort of debugging/dev work.
agentdr8 said:
......
I've run across at least one xposed module out there that bypasses the AOSP email security restrictions for EAS. Since I don't normally run AOSP roms, it's much harder for me to do any sort of debugging/dev work.
Click to expand...
Click to collapse
Can you tell me where to find the modules to bypass these security restrictions for EAS. There are indeed some modules to bypass the mandatory PIN for example. But no module to bypass and change the device provisioning data.
This is what I needed thanks will try and report
yooidje said:
Can you tell me where to find the modules to bypass these security restrictions for EAS. There are indeed some modules to bypass the mandatory PIN for example. But no module to bypass and change the device provisioning data.
Click to expand...
Click to collapse
You're right; I don't think any of the ones I've seen can modify the device provisioning data, only bypass the PIN/lockscreen restrictions.
agentdr8 said:
You're right; I don't think any of the ones I've seen can modify the device provisioning data, only bypass the PIN/lockscreen restrictions.
Click to expand...
Click to collapse
Is there any possibility that you can also support the AOSP email apps, perhaps?
**please :angel:
yooidje said:
Is there any possibility that you can also support the AOSP email apps, perhaps?
**please :angel:
Click to expand...
Click to collapse
If I have some free time I'll see what I can do on my TF700 running CM11.
agentdr8 said:
If I have some free time I'll see what I can do on my TF700 running CM11.
Click to expand...
Click to collapse
:victory: I am more than willing to test any developments
In case anyone is wondering, this module still works on LP with the latest Xposed Framework.
Still working on the latest Xposed Framework for Marshmallow. Also tested against O365, and works just fine.
agentdr8 said:
Still working on the latest Xposed Framework for Marshmallow. Also tested against O365, and works just fine.
Click to expand...
Click to collapse
Hi, can you confirm if this works with the latest version of touchdown available currently, 8.5?
randallstevens said:
Hi, can you confirm if this works with the latest version of touchdown available currently, 8.5?
Click to expand...
Click to collapse
Yes indeed. I'm running 8.5.00086 with the module just fine. I'll update the OP.
EDIT: Looks like I had already updated the OP with that info. [emoji3]
SIM Number SetterSIM Number Setter is a small Xposed module that invokes normally unused Android System code to set the "subscriber number" on the device's SIM card. This is the number displayed in the system settings, and used in apps such as Google Messages, as well as being available to third party apps with sufficient permissions.
The number is not always set by carriers (leaving "Unknown"), or can be lost or invalid after porting a number to a different SIM.
This small app allows you to fix it, permanently, using a rooted device with Xposed.
If you don't have a rooted device, or don't want to root your main device, you may wish to consider rooting an old device, and temporarily putting your SIM into that device, using this app, and then putting it back in your main device - the fixed number will travel with it
There are some older Xposed modules that do similar things to this, but they are all abandoned and use methods that will no longer work with changes to the platform since then. This module should keep working regardless as it does not store the number locally at all, instead immediately invoking the change - allowing the app to be uninstalled after use too.
Important NoticeChanging the SIM number is semi-permanent: the number change will survive reboots, uninstalling this app, even switching the SIM to a different device, but can be changed again at any time using this app.
SIM Number Setter does NOT:
Change your actual phone number, no matter what you enter. You must contact your carrier if you wish to port your number or switch network.
Unblock a network blocked SIM.
Give you free data or calls.
Change your IMEI.
SIM Number Setter uses the built-in Android methods to write data to the SIM. The app nor the developer are not responsible for issues with the process, including any damage to the SIM or network issues.
Screenshots
DownloadDownload from the GitHub releases page
Source Code
GitHub
It works perfectly fine with LSposed too!!
Thanks a lot!
Ohh, FFS! If you have dual SIM, just switch them, change its number and switch them back! Not a big deal!
@Quinny899 Thanks for this! Is there a defined format in which the phone number should be entered? For example, +[Country Code][10 Digit Mobile Number], or 00[Country Code][10 Digit Mobile Number], something like that?
shadowstep said:
@Quinny899 Thanks for this! Is there a defined format in which the phone number should be entered? For example, +[Country Code][10 Digit Mobile Number], or 00[Country Code][10 Digit Mobile Number], something like that?
Click to expand...
Click to collapse
Anything should work, so long as it's 20 chars or less and uses only numbers or +
works perfectly as described, in case of dual SIM just temporarily change the position to SIM1
brenosnt said:
works perfectly as described, in case of dual SIM just temporarily change the position to SIM1
Click to expand...
Click to collapse
I concur! working wonderfully on Android 12 Beyond Rom (Note 20 Ultra)!!
Quinny899 said:
Anything should work, so long as it's 20 chars or less and uses only numbers or +
Click to expand...
Click to collapse
Doesn't work for me, unfortunately. Could be because of OxygenOS (read all the issues, open and closed, in your GitHub repository and checked everything) but I'm not sure. Thanks nonetheless!
rgavioli said:
It works perfectly fine with LSposed too!!
Click to expand...
Click to collapse
Can u help me, I'm getting failed to connect to the Xposed service.
Already have LSposed zygisk installed and I enabled module.
Running android 12
fardeenah said:
Can u help me, I'm getting failed to connect to the Xposed service.
Already have LSposed zygisk installed and I enabled module.
Running android 12
Click to expand...
Click to collapse
Which Android 12 firmware on what device?
Quinny899 said:
Which Android 12 firmware on what device?
Click to expand...
Click to collapse
Running AEX aospextended on redmi note 5 pro
fardeenah said:
Running AEX aospextended on redmi note 5 pro
Click to expand...
Click to collapse
There's a report on GitHub of someone with a phone that came with MIUI doing the same thing, I suspect there's something different on those devices. Not a lot I can do without having the device to debug, as the logs don't show anything.
F
Quinny899 said:
There's a report on GitHub of someone with a phone that came with MIUI doing the same thing, I suspect there's something different on those devices. Not a lot I can do without having the device to debug, as the logs don't show anything
Click to expand...
Click to collapse
I really wish I could change that sim number. Man....
Such a bummer.
Make sure the module is enabled on LSposed.
Also, make sure Phone services is selected at the module.
Reboot your device and try again.
{
"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"
}
rgavioli said:
Make sure the module is enabled on LSposed.
Also, make sure Phone services is selected at the module.
Reboot your device and try again.
View attachment 5543693
Click to expand...
Click to collapse
I did but it's not working for me.. What device are you running btw? Are u using the latest version of LSposed
fardeenah said:
I did but it's not working for me.. What device are you running btw? Are u using the latest version of LSposed
Click to expand...
Click to collapse
I've tested on Samsung S20, Xiaomi Mi11i and it works fine.
LSposed 1.7.2 (6379)
You could try cleaning the data from this app.
Thank you for this. I just ported my Mobile Number to another network and got a unknown number on about phone.
Just a question. Is the write procedure single use?
Can you re-write the field if you transfer numbers, or misstype, or, or or?
AndStuff said:
Just a question. Is the write procedure single use?
Can you re-write the field if you transfer numbers, or misstype, or, or or?
Click to expand...
Click to collapse
You can rewrite it as many times as you like, though I'd recommend trying to keep usage low as I doubt SIMs are designed for this data to be rewritten often. If you make a typo you can fix it though.
{
"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"
}
Let Me DowngradeAndroid's app installation system does not allow users to downgrade to an older version of an app when they already have a newer version installed. Let Me Downgrade is an Xposed module for Android 12 and 13 that enables users to bypass this restriction. As an added bonus, Let Me Downgrade provides a Quick Settings tile to easily enable and disable the downgrade block.
WARNING: Let Me Downgrade is intended for rooted devices running Android 12 or 13 and requires Xposed. The recommended Xposed variant to use is LSPosed. Other Xposed variants may work, but have not been tested. Additionally, this module cannot be guaranteed to work on all devices. In the worst case, it can cause a bootloop. Use at your own risk.
To use Let Me Downgrade:
Install LSposed. This requires your device to be rooted with Magisk. Installation instructions for LSPosed are available here.
Install Let Me Downgrade.
Activate the Let Me Downgrade module in the LSposed user interface.
Reboot your device and sign in.
Open the quick settings panel. The Let Me Downgrade tile will appear.
Toggle the Let Me Downgrade tile on or off to enable or disable it.
Reserved.
Reserved.
Nice work! I assume this does not have backward compatibility, i.e. it won't work on older Android versions, and only supports Android 13? Also, consider submitting it in the Xposed-Modules-Repo.
shadowstep said:
Nice work! I assume this does not have backward compatibility, i.e. it won't work on older Android versions, and only supports Android 13? Also, consider submitting it in the Xposed-Modules-Repo.
Click to expand...
Click to collapse
Thank you! Unfortunately, this does not have backwards compatibility with older versions of Android. Adding support for allowing downgrades on Android 5 through 12 would actually be pretty easy, but adding support for the quick settings tile to toggle the module on and off would not be, and I do not really think that it is worth the effort of doing so considering that anyone using Android 5-12 will probably already be using XDowngrader.
I should also note that the developer of XDowngrader actually published an update to support Android 13 soon after I published this module, however I would recommend that Android 13 users opt for my module instead because:
Let Me Downgrade is open source but XDowngrader is not.
Let Me Downgrade allows you to toggle the module's functionality on and off without rebooting your phone through a Quick Settings tile. This is useful for if you want to temporarily allow app downgrades, but would prefer to leave app downgrades disabled in most other cases.
As far as publishing on the Xposed Modules Repo is concerned, I have actually done that! The repo entry for this module is available here.
Could you add support for android 11 and 12. That would be pretty nice!
Lucky_069 said:
Could you add support for android 11 and 12. That would be pretty nice!
Click to expand...
Click to collapse
I can add support for Android 12 pretty easily, but anything older than that, I don't think so because the Quick Settings tiles may not work and I don't have a phone to test it on.
For the convenience of users who prefer to not use the Google Play Store, I am pleased to announce that Let Me Downgrade is now available on F-Droid!
Let Me Downgrade | F-Droid - Free and Open Source Android App Repository
Add support for downgrading apps on Android 12 and 13
f-droid.org
Several users have requested support for Android 12. I am pleased to announce that Let Me Downgrade v1.0.2 adds this support.
Now I follow all steps but how I can start the downgrade?
xerel89 said:
Now I follow all steps but how I can start the downgrade?
Click to expand...
Click to collapse
After enabling the module, the downgrade process is no different than the installation or update process that you use when sideloading an app. You can use ADB to do it or you can use a file explorer app to install the older version of the app.
Not sure I get it... If I want to go back to an older version of an app, can't I just clear it's cache and uninstall the new ver. then install the old one?
Zaxx32 said:
Not sure I get it... If I want to go back to an older version of an app, can't I just clear it's cache and uninstall the new ver. then install the old one?
Click to expand...
Click to collapse
You can, but that would mean you would lose your app settings. If you use Let Me Downgrade, you'll be able to install the old version on top of the old one and retain your settings. Please note however that just because you downgrade your app in place does not mean things will work if the newer version has made internal structural changes to how the data is stored.
Gotcha!
Any way you could add the ability to disable signature verification as well?
bobpiesz said:
Any way you could add the ability to disable signature verification as well?
Click to expand...
Click to collapse
It would probably be more appropriate for me to make that be a separate module, but yes, it is possible.
@David B.
I'd be more than willing to donate towards having disable signature verification, as I'm not finding any publicly available tools for A13
bobpiesz said:
@David B.
I'd be more than willing to donate towards having disable signature verification, as I'm not finding any publicly available tools for A13
Click to expand...
Click to collapse
Doesn't Core Patch support this?
GitHub - LSPosed/CorePatch: Disable signature verification For Android
Disable signature verification For Android. Contribute to LSPosed/CorePatch development by creating an account on GitHub.
github.com
David B. said:
It would probably be more appropriate for me to make that be a separate module, but yes, it is possible.
Click to expand...
Click to collapse
Lord Sithek said:
Doesn't Core Patch support this?
GitHub - LSPosed/CorePatch: Disable signature verification For Android
Disable signature verification For Android. Contribute to LSPosed/CorePatch development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Core patch isn't working with A13
bobpiesz said:
@David B.
I'd be more than willing to donate towards having disable signature verification, as I'm not finding any publicly available tools for A13
Click to expand...
Click to collapse
When time permits, I can and will research this. Unfortunately, I'm preoccupied with other things at the moment and have had to set aside doing Xposed module development work. If you or anyone else wants to experiment and submit a PR for it, that would be greatly appreciated.
Lord Sithek said:
Doesn't Core Patch support this?
GitHub - LSPosed/CorePatch: Disable signature verification For Android
Disable signature verification For Android. Contribute to LSPosed/CorePatch development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
bobpiesz said:
Core patch isn't working with A13
Click to expand...
Click to collapse
Thank you for sharing Core Patch. I wasn't aware of its existence. Even though it doesn't work on Android 13, it might be able to serve as a good resource for me to figure out where I need to hook.
Hello,
I've trying to install Viper4Android on the Zenfone for the past 2 days, but with no success I keep getting the Driver Not Found even after adjusting the post-fs-data.sh files with the proper locations. Also tried multiple fixes from other threads . My question is has anybody managed to get the Module to run?
Update: It seems the application is processing my headphones when it's connected, but still cannot get it to install the drivers
{
"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"
}
Thecurse21 said:
Hello,
I've trying to install Viper4Android on the Zenfone for the past 2 days, but with no success I keep getting the Driver Not Found even after adjusting the post-fs-data.sh files with the proper locations. Also tried multiple fixes from other threads . My question is has anybody managed to get the Module to run?
Click to expand...
Click to collapse
No. I tried several ways and always same issue..... other audio mods not working too
Update on this Thread since the Zenfone 9 probably has 64 bit audio drivers, viper4android uses 32bit and cannot be used until it is updated for 64bit, which the devs of V4A are working on, hopefully soon enough our ears will be able to enjoy better sound.
@Thecurse21 message me on telegram, I have a 64 bit test version you could try https://t.me/iscle
iscle said:
@Thecurse21 message me on telegram, I have a 64 bit test version you could try https://t.me/iscle
Click to expand...
Click to collapse
Any chance that this test version would work on Pixel 6/7 devices with A13? Thanks
EthanG_1988 said:
Any chance that this test version would work on Pixel 6/7 devices with A13? Thanks
Click to expand...
Click to collapse
Yes, it does, it's already been tested
iscle said:
Yes, it does, it's already been tested
Click to expand...
Click to collapse
Awesome. Thanks! Looking forward to it...miss having quality sound lol.
iscle said:
@Thecurse21 message me on telegram, I have a 64 bit test version you could try https://t.me/iscle
Click to expand...
Click to collapse
Could you share me the 64 bit test version？thanks a lot，I have PM you on telegram.
iscle said:
@Thecurse21 message me on telegram, I have a 64 bit test version you could try https://t.me/iscle
Click to expand...
Click to collapse
I also send you a message on telegram yesterday. i think its best if you could share it publicly here so more people can test it and provide feedback.
palamosteliaro said:
I also send you a message on telegram yesterday. i think its best if you could share it publicly here so more people can test it and provide feedback.
Click to expand...
Click to collapse
I would share it, but I've been told it contains code that they don't want to be made public, so after that code is removed probably they will maybe do a beta test or something, until then probably better to ask in the telegram chat or DM for the files. So far the working things for me were the Clarity and Bass, but the dynamic system doesn't work properly for me at least.
Thecurse21 said:
I would share it, but I've been told it contains code that they don't want to be made public, so after that code is removed probably they will maybe do a beta test or something, until then probably better to ask in the telegram chat or DM for the files. So far the working things for me were the Clarity and Bass, but the dynamic system doesn't work properly for me at least.
Click to expand...
Click to collapse
Oh i think it's better to wait then. I never really understood telegram, so could you provide a link where i can keep track of the progress? Is 64bit an official effort from those who initially developed v4a, or from the community?
I really can't understand how manufacturers can't even come close to the quality of v4a on their integrated DSPs. The one in the Zenfone is pretty good, but still far from what you can do on v4a.
palamosteliaro said:
Oh i think it's better to wait then. I never really understood telegram, so could you provide a link where i can keep track of the progress? Is 64bit an official effort from those who initially developed v4a, or from the community?
I really can't understand how manufacturers can't even come close to the quality of v4a on their integrated DSPs. The one in the Zenfone is pretty good, but still far from what you can do on v4a.
Click to expand...
Click to collapse
https://t.me/ViPER4AndroidFXchannel Here is the official link just open it in Telegram
Thecurse21 said:
https://t.me/ViPER4AndroidFXchannel Here is the official link just open it in Telegram
Click to expand...
Click to collapse
yes i stumbled upon this a while back, but there hasn't been an update for s year so i thought it's not active anymore. I will keep checking it thanks!
Update: The developers have released an 64bit version of V4A I've installed and it works. Some of the features are not yet available due to the release being in an Alpha, but we finally have a working 64bit version working.
Here is the link for the build: https://github.com/AndroidAudioMods/ViPER4AndroidApp/releases/tag/v0.1.0
Does Not Work for me with VLC. Do i need to install audio compability patch? Installation fails with hint audio modification lib is missing. Where can i find latest acp binary? On GitHub i can only find source.
Thecurse21 said:
Update: The developers have released an 64bit version of V4A I've installed and it works. Some of the features are not yet available due to the release being in an Alpha, but we finally have a working 64bit version working.
Here is the link for the build: https://github.com/AndroidAudioMods/ViPER4AndroidApp/releases/tag/v0.1.0
Click to expand...
Click to collapse
Thanks for the update bro
Hermann2306 said:
Does Not Work for me with VLC. Do i need to install audio compability patch? Installation fails with hint audio modification lib is missing. Where can i find latest acp binary? On GitHub i can only find source.
Click to expand...
Click to collapse
Its working with VLC (and everything else) here on latest Android 13. To make it start processing, you need to close all audio apps from the notification bar and enable legacy mode inside the option in the app. I didn't install the compatibility patch.
Keep in mind its not like the old version, the application won't even ask for root access or install the driver and restart like it used to. If you close everything that plays music and enable legacy mode a few times it will work.
palamosteliaro said:
Keep in mind its not like the old version, the application won't even ask for root access or install the driver and restart like it used to. If you close everything that plays music and enable legacy mode a few times it will work.
Click to expand...
Click to collapse
Tried this, still not working
ikramahmed said:
Tried this, still not working
View attachment 5800409
Click to expand...
Click to collapse
Working now after turning off LDAC
I cant get driver status enabled yes. Even if i switch legacy mode on/off (maybe) 25 times.
Im trying without bluetooth connection, will test the ldac option with bluetooth tomorrow in car.
Hermann2306 said:
I cant get driver status enabled yes. Even if i switch legacy mode on/off (maybe) 25 times.
Im trying without bluetooth connection, will test the ldac option with bluetooth tomorrow in car.
Click to expand...
Click to collapse
I had to turn off LDAC in the soundcore app on my phone so I'm guessing it does not support LDAC.
Download: https://github.com/ponces/treble_build_aosp/releases
TEST: DeGoogle GSI only exFAT sd card supported.
☆☆ Create LeOS TD for support exFAT and works smoothly.
Degoogle (LeOS-T April 2023 Only ) A13 GSI Run with exFAT SD card supported.
Supported exFAT only 1 Variant LeOS-T April 2023 Only ============================ Step to install LeOS-T GSI Variant. DOWNLOAD--firmware from https://samfw.com/ 0. Create patch-recovery for fastbootD ☆☆☆ FastbootD video tutorial ...
forum.xda-developers.com
☆☆ AOSP A13 vs AOSP Android 14☆☆
☆☆☆ FastbootD video tutorial : https://m.youtube.com/playlist?list=PLvggR4skCxYzhB3SXxpSx4LvRzGwx9k45
Based on android-13.0.0_r44
TREBLE DROID Phh android_13.0.0_r41 ci-20230429 (https://github.com/TrebleDroid/treble_experimentations/releases/tag/ci-20230429)
==============≠={{
✓ Pure AOSP A13 From Ponces Developer.
AOSP 13.0 v2023.05.03
{
"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"
}
First boot
Change default Home-Launcher.( Test Float Launcher )
✓Bluetooth:
no problem about connectivity.
✓No Offline charging function.
✓During power-on device we must insert charging cable before turn-off your tablet.
update: Next 》》》 Mod New Float and auto-hide Navigation.
Do you want try this :https://forum.xda-developers.com/t/closed-one-ui-gsi-to-all-samsung.4543881/
May be we can upgrade to one ui 6.0 with gsi on some day
Difficul said:
Do you want try this :https://forum.xda-developers.com/t/closed-one-ui-gsi-to-all-samsung.4543881/
May be we can upgrade to one ui 6.0 with gsi on some day
Click to expand...
Click to collapse
Do not promote thread closed. Drink coffee better my friends.
Thank you so much, I've been looking for a pure AOSP w/ Gapps rom for a bit. Testing it w/o any issues so far.
@tom.android is auto brightness working? I can see the light sensor reading but no option to enable it.
hackthis02 said:
@tom.android is auto brightness working? I can see the light sensor reading but no option to enable it.
Click to expand...
Click to collapse
must make overlay for it.
tom.android said:
must make overlay for it.
Click to expand...
Click to collapse
I made this one last night but wasn't able to get it working. Either I did it wrong, following phhusson wiki. Or there is more to it than putting it in /system/vendor/overlay and changing the permissions.
hackthis02 said:
I made this one last night but wasn't able to get it working. Either I did it wrong, following phhusson wiki. Or there is more to it than putting it in /system/vendor/overlay and changing the permissions.
Click to expand...
Click to collapse
If you have Magisk installed, that's an easy way to install an alternative overlay apk, otherwise putting it in /system/vendor/overlay should work if the overlay is valid. Here's the overlay I made for myself along with the Magisk module I created in order to install it.
Hai Karate said:
If you have Magisk installed, that's an easy way to install an alternative overlay apk, otherwise putting it in /system/vendor/overlay should work if the overlay is valid. Here's the overlay I made for myself along with the Magisk module I created in order to install it.
Click to expand...
Click to collapse
I wasn't using Magisk, but I flashed it and it seems to be working. Thanks.
hackthis02 said:
I wasn't using Magisk, but I flashed it and it seems to be working. Thanks.
Click to expand...
Click to collapse
Ok if it not works , pm me again.
NOTE: Try to see both auto screen brightness and individual power usages history works also.
tom.android said:
Ok if it not works , pm me again.
NOTE: Try to see both auto screen brightness and individual power usages history works also.
Click to expand...
Click to collapse
@Hai Karate module fixed Auto brightness. Do you mean this for power usage?
hackthis02 said:
@Hai Karate module fixed Auto brightness. Do you mean this for power usage?
View attachment 5903171
Click to expand...
Click to collapse
Ya it ok
@tom.android how did you enable the floating taskbar in your screenshots? My still looks like the QPR1 version.
hackthis02 said:
@tom.android how did you enable the floating taskbar in your screenshots? My still looks like the QPR1 version.
Click to expand...
Click to collapse
It was my mod launcher for LeOS-T (A13 PQR-2) Floating Main Navigation) can enable from developer Options menu. ( Can't run on Ponces' s AOSP A13 GSI. test mode only.
Hey ! Someone can send me tha AP file i really wanted to try this GSI i am student & i really don't understand how to make AP file ! Sm-t220
Sakuna said:
Hey ! Someone can send me tha AP file i really wanted to try this GSI i am student & i really don't understand how to make AP file ! Sm-t220
Click to expand...
Click to collapse
Custom AP is inconvenient
You should try TWRP or stock recovery path with fastbootd found
Sakuna said:
Hey ! Someone can send me tha AP file i really wanted to try this GSI i am student & i really don't understand how to make AP file ! Sm-t220
Click to expand...
Click to collapse
Read my tutorial here.
New update
"AOSP 13.0 v2023.05.18"
Android OS version: 13.0.0_r49
Download: https://github.com/ponces/treble_build_aosp/releases
What new ?
Test with DSU Sideloader.
Video: uploading....