editing the build.prop on android 11 - General Questions and Answers

editing the build.prop on android 11 - General Questions and Answers

So I finally upgraded from my oneplus 7 pro to a oneplus 8t. I'm loving the phone and I found 2 or 3 custom rom options I like.
The problem I keep running into is that I need to modify my build.prop because an app I need to use for work "only runs on samsungs". I've been using my 7 pro for over a year with no problems because I just type in galaxy s8 info to the build.prop.
When I try and modify the build.prop on any android 11 rom, the phone stops booting past the bootloader unlocked screen. I can quickly get back by using fastboot rominstaller.
I've tried using multiple build.prop apps, I've tried editing the file through root managers, I've tried moving it to a different folder then editing it and putting it back and that doesn't work either. I tried magiskhide props config and it looks like it works but doesn't.
Did something happen with android 11? I don't even know where to start on this.
Thanks for absolutely any help at all

f2bacon said:
I tried magiskhide props config and it looks like it works but doesn't.
Click to expand...
Click to collapse
If you post a detailed description of what you've tried and why you say that it doesn't work in the MagiskHide Props Config thread, preferably with the module logs attached, I might be able to help with that at least...

i'll do that, thank you very much

Related

Root on fire HD 10 - but no custom recovery or ROMs?

Can someone help me understand how we can have root methods for the HD 10, but no custom recovery or ROMs?
Any news or updates on the effort here? I'm willing to pay or donate to get it done!
I REALLY want to turn my tablet into an Android tablet... Not a fire tablet with an almost Android experience.

If we can get some one to create safestrap probably we can have a custom Rom !ade

There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.

DragonFire1024 said:
There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.
Click to expand...
Click to collapse
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!

Supersonic27543 said:
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!
Click to expand...
Click to collapse
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.

DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!

Supersonic27543 said:
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!
Click to expand...
Click to collapse
That's one of my projects

DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Could be that I don't know how to solve the problems I have, but for me not all the Google play applications I want (for my kid) work. Issues vary from validating my authorized purchase to core functionality of applications not working. Some of the applications refer to Android os content and services that either aren't in fire os, are named differently, or have different functionality.
Not to mention that I dislike my son's user experience... He's only 3, quite smart but I've not been able to strike a good balance of protecting him and allowing him to actually use his tablet without learning wierd tricks to access Google play apps.
I'm ok if I have to stay on Fire Os if I can have complete control over profiles, launchers and have a genuine experience using my Google Play applications. Some of the FreeTime stuff is ok... My son might like some of it. But more importantly I want him to have the far superior applications on Google Play which are not currently available on Fire.

I'm willing to contribute to get a custom rom on the fire 10.

I really want to compile one, my skills are getting blunt without some compiling, but it turns out that I only have a HD 8.

Can someone please educate me on getting the GPS to work with google maps, like my phone? My HD 10 7th gen is rooted w/supersu. I have xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.

kferling said:
Can someone please educate me on getting the GPS to work with google maps, naively like my phone? My HD 10 7th gen is rooted w/supersu. I have Xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.
Click to expand...
Click to collapse
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Click to expand...
Click to collapse
Thanks, although I did not get location prompts at the end. :/
Data was wiped for all 4, and uninstalled. rebooted and verified no data with ES.
Installed google apks in the exact order, waited 2 minutes, rebooted, then logged into playstore.
Went to home screen, saw apps flash after waiting. Went to location services (was off) turned on and no prompts
Turned off, waited 30 secs, turned back on, still no prompts.
Is this any different from your guide here?
Step 6. states "Once all the APKs are installed, open the Play Store and sign into your account and IMMEDIATELY go to settings and TURN OFF auto-updates. "
Perhaps that's what I need to do?

Just ordered an HD10, will this tutorial still work? https://forum.xda-developers.com/hd...7-root-box-t3726443/post75187398#post75187398
Will that debloat Fire OS also?

So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.

Have a new 2015 HD 10. Will definitely be following your progress

FuNKSioN said:
Have a new 2015 HD 10. Will definitely be following your progress
Click to expand...
Click to collapse
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.

TechNash said:
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.
Click to expand...
Click to collapse
Not sure about the encryption. It has to be a script problem, or the system partition won't accept zips and that's the barrier. However if I just flash the system directory instead, everything works fine. I can flash stuff into it just fine that way, but seems any time I go the way of the partition, I can't win. Flashing your own system image works too. However I haven't been able to get one to flash if I modify it. So I can decompile a system.img add to it, remove items and recompile it and it won't flash.
I am using flash fire to flash zips. We still have a locked bootloader so twrp isn't a likely option.
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.
Click to expand...
Click to collapse
I mean, if PC performance is an issue I can give you access to a brand new xeon if it means there will be a custom ROM out.
Been thinking about buying the Fire HD 10 this black Friday and flash the Amazon garbage out, and was amazed to see none exist even though it has been a year since they figured out the rooting.
This will be an outstanding value if it was possible...

[Guide] Enable VoWiFi on custom ROMs

First attempt at making a guide for this, so please feel free to make suggestions on how to clean it up (I feel like it doesn't lend itself well to step-by-step but you're welcome to try).
Great news everyone! (well, all three of us with T-Mobile/MetroPCS in the USA...)
I got VoWiFi to work last night on a couple custom ROMs and successfully made wifi calls. It doesn't require many pieces, but it can be complicated (not just a step-by-step) to get the required pieces into the right places.
- You need a copy of /system/priv-app/CNEService/CNEService.apk from a stock OOS install (I did it with the one from 9.0.3).
To get that, you might be looking at booting into TWRP with the other slot active or temporarily using something like @mauronofrio's fastboot install ROM from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and just flashing the system image to one slot to grab the file before restoring back to the one you had. Anyway, use caution, be sure of which slot you're on and what you're flashing to, and copy the apk from /system/system/priv-app (the path when you're booted from TWRP instead of inside the active system slot). You'll probably have to use ADB commands to push/pull the file directly to/from a computer if you already have a custom rom installed on one slot with screen lock set up, since /data will likely be encrypted and unavailable when you're booted up in TWRP with the other stock slot active.
- You need to be able to install a rando apk as a privileged system app to get this apk back into /system/priv-app/ correctly on your custom ROM.
There are ways to do this manually that involve lots of permissions and editing XML files for privileged app permissions in a couple places, but realistically you're using a custom ROM so you probably have Magisk (otherwise what the hell are you doing with custom ROMs?) so you should just use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 and pick option 3 to install it. You'll need Magisk, a terminal emulator, and some ability to type a file path to use this module.
- You'll need to make sure that your /system/build.prop file contains the line "persist.vendor.cne.feature=1" (AEX doesn't at first, XenonHD does, not sure about others).
We've got the requisite stuff in /vendor already, this just enables the ability to use it. You'll need to have root access and a file manager/text editor (Amaze is FOSS and available through F-Droid, MixPlorer through XDA Labs is also nice, or use TWRP and a text editor that knows unix line endings on your computer to copy things back & forth via MTP and remember to set permissions after, I think it's chmod 644).
Reboot, unlock, and try to make a test call. Successfully got it to work on AEX & XenonHD last night, I suspect it works for Omni and others as well.
Try some more ROMs out and report back below if it works for you too!

Now if only you could fix the Android Auto bug.
I'm totally kidding. This is awesome. Thank you!

Tested Omni and it works too; just needed the APK added/systemized, already has the correct entry in build.prop.

hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??

Any chance someone could upload and share the CNEService.apk? Would make life a lot easier...

brmbjn said:
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Click to expand...
Click to collapse
If it's not working in OOS, I don't know what to tell you. Might just be that the connection isn't reliable enough for it to decide to enable... but I never used OB10; I switched back to stable 9.0.3 after OB9.

Great work!

[CLOSED][Magisk Module] Framework-res Mod OnePlus 7 Oxygen OS Stable/Beta

Hi,
I am happy to share my Framework-res mod, specific for Oneplus 7 with Openbeta firmware.
My work includes the following changes:
- Disabled keyboard switcher notification
- Disabled high volume warning
- Enabled burnin protection
- Changed battery notification low level from 15% to 10%
- Enabled 360° rotation
- Reduced navigation bar height from 48dp to 41dp
It is a magisk module and I want to repeat that it can only be used on Oneplus 7 with Openbeta firmware
I'm trying it and it doesn't seem to show any problems but I still recommend making a backup before trying it.
To remove the mod, simply uninstall the module using magisk manager or, if this is not usable, from recovery twrp, using the file manager deleting the module "Framework-res mods" that you find at the following path:
/data/adb/modules
My big thanks go to @Tulsadiver, for giving me the right tips to be able to make the mod and for passing me the VRThemer module, without His help I would not have been able to avoid the bootloop
P.S. If you want the mod for other firmware versions, please send me your framework-res.apk and I will prepare the specific module.
If you want to try making the mod yourself, check out the tutorial here
Flashing always at your own risk!!!

20th March 2020 - Added OnePlus 7 OpenBeta 11 specific module

Thanks for your work, My kernel is Kirisakura-Kernel. Can I use it?

foolo said:
Thanks for your work, My kernel is Kirisakura-Kernel. Can I use it?
Click to expand...
Click to collapse
It works with any oxygenos based software (it doesn't work with AOSP rom) regardless of the kernel used
Could you pass me the framework-res.apk of the stable version? I would also like to prepare the specific mod for OxygenOS stable version.
Thank you.

Thanks. Worked perfectly.

Added OnePlus 7 OpenBeta 12 specific module to the first post

This is the framework-res.apk for the stable 10.3.1 oxygen os oneplus 7. Could you make a version for this too? I could help with the testing. Thank you!
(Uploading drive link cause xda doesn' t allow upload of apk more than 20MB.)
https://drive.google.com/file/d/1OagIggcj_WUKcuOYQKOsUNYaCQaA04Ev/view?usp=drivesdk

neildalal said:
This is the framework-res.apk for the stable 10.3.1 oxygen os oneplus 7. Could you make a version for this too? I could help with the testing. Thank you!
Click to expand...
Click to collapse
Done!
Added OnePlus 7 Oxygen OS Stable 10.3.1 specific module to the first post

dianoandr said:
Done!
Added OnePlus 7 Oxygen OS Stable 10.3.1 specific module to the first post
Click to expand...
Click to collapse
Just flashed via magisk and works perfectly fine!
Thank you!!

Added OnePlus 7 OpenBeta 13 specific module to the first post

Added OnePlus 7 OpenBeta 14 specific module to the first post

Added OnePlus 7 OpenBeta 15 module to the first post

dianoandr said:
Added OnePlus 7 OpenBeta 15 module to the first post
Click to expand...
Click to collapse
Thanks for u hard work .
Can you make mod for stable 10.0.6Gm57BA EU version?

M.Kader said:
Thanks for u hard work .
Can you make mod for stable 10.0.6Gm57BA EU version?
Click to expand...
Click to collapse
Sure it is possible!
I need the stock framework-res.apk from 10.0.6Gm57BA firmware, If You or Someone else who uses this firmware extracts it and sends it to me, I create the specific firmware magisk module

Added to the first post the module for OnePlus 7 OpenBeta 16 firmware.

Hi there @dianoandr
I have been trying to modify my OP7T framework-res apk to edit the vibe pattern which is contained under arrays.xml in values folder. However I haven't had any luck since I have always ended in a bootloop and needing to delete module. Could u help me out?
Thanks!

miguelang611 said:
Hi there @dianoandr
I have been trying to modify my OP7T framework-res apk to edit the vibe pattern which is contained under arrays.xml in values folder. However I haven't had any luck since I have always ended in a bootloop and needing to delete module. Could u help me out?
Thanks!
Click to expand...
Click to collapse
Hi @miguelang611,
Probably the bootloop occurs because you directly use the modified apk that is created by "apk tool", also I had this problem, try to use my module replacing the contents of the folder "vrtheme \ system \ framework \ framework-res.apk " with your modified files, extract the contents of your modified apk and copy in the magisk module everything EXCEPT for the meta-inf folder and the android-manifest file.
Try this and update me.
Regards!

dianoandr said:
Hi @miguelang611,
Probably the bootloop occurs because you directly use the modified apk that is created by "apk tool", also I had this problem, try to use my module replacing the contents of the folder "vrtheme \ system \ framework \ framework-res.apk " with your modified files, extract the contents of your modified apk and copy in the magisk module everything EXCEPT for the meta-inf folder and the android-manifest file.
Try this and update me.
Regards!
Click to expand...
Click to collapse
Thank u dude
The Friday after lot of tests reached to same conclusion as yours: copy everything from TMA (what I used to decompile) and once I removed the meta-inf and manifest, boom, it worked!
However, unfortunately I couldn't manage to edit vibration on arrays, since changing values there made 0 difference to actual phone vibration.
Saw that under public.xml there are also some vibe pattern, but neither worked
At least I got a way of fully modifying the framework and still booting
Thanks!

miguelang611 said:
Thank u dude
The Friday after lot of tests reached to same conclusion as yours: copy everything from TMA (what I used to decompile) and once I removed the meta-inf and manifest, boom, it worked!
However, unfortunately I couldn't manage to edit vibration on arrays, since changing values there made 0 difference to actual phone vibration.
Saw that under public.xml there are also some vibe pattern, but neither worked
At least I got a way of fully modifying the framework and still booting
Thanks!
Click to expand...
Click to collapse
No problem, it was a pleasure
If I make no mistakes, the vibration patterns are also determined by the kernel, but honestly, I never went into that.
Regards!

dianoandr said:
No problem, it was a pleasure
If I make no mistakes, the vibration patterns are also determined by the kernel, but honestly, I never went into that.
Regards!
Click to expand...
Click to collapse
With kernel y can change intensity, but I wanna change duration (just as clock, SMS or calls do)
Not found yet though, still looking for the way to go
Thanks again!

[HELP!!!] Making Viper4Android work in Samsung SnapDragon

Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!

Also fellow S22U Snapdragon owner here (S908N). I've been seeing you around the threads as I am also trying to get Viper working on this thing. Hope you find a way to get it working, I hope you'll share the steps if you can make it work. Best of luck.
If you want an accelerated progress you might have to put a bounty on this.

ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
Okay, I got JamesDSP working now. Had to install AML, and then install JameDSP with the Huawei installation method. I'm gonna try to flash Viper on see if that does anything.

Fireburito said:
Okay, I got JamesDSP working now. Had to install AML, and then install JameDSP with the Huawei installation method. I'm gonna try to flash Viper on see if that does anything.
Click to expand...
Click to collapse
I tried that too. I can get Jamesdsp to work, but it is way inferior to V4A. At least I couldn't get a good bass from it.
I know several other users that want that too. It would be nice to have someone who knows the working of V4A to help or at least a S21 SD owner to share his files and codes, maybe we can copy them.
What you mean by bounty? I ambwilling to try anything for this to work and I will not stop until we make it. The main reason I rooted this damn thing was to get V4A.

ffp. said:
I tried that too. I can get Jamesdsp to work, but it is way inferior to V4A. At least I couldn't get a good bass from it.
I know several other users that want that too. It would be nice to have someone who knows the working of V4A to help or at least a S21 SD owner to share his files and codes, maybe we can copy them.
What you mean by bounty? I ambwilling to try anything for this to work and I will not stop until we make it. The main reason I rooted this damn thing was to get V4A.
Click to expand...
Click to collapse
Yeah, before I couldn't even get JamesDSP to work, so just having it now as some form sound mod is semi-okay. I'm trying to use that to piggyback off to install Viper, but to no avail.
I think it's something with the Huawei install method that got it working ? As installing with the normal method before just made the app crash. The module files in JamesDSP correctly targeted the sku-taro folders too, unlike Viper.
A bounty is basically you post a reward amount to any dev that can get Viper working on our SD S22U, it will at least get some experienced and knowledgeable people onboard trying to figure it out instead of us grasping at straws.

Fireburito said:
Yeah, before I couldn't even get JamesDSP to work, so just having it now as some form sound mod is semi-okay. I'm trying to use that to piggyback off to install Viper, but to no avail.
I think it's something with the Huawei install method that got it working ? As installing with the normal method before just made the app crash. The module files in JamesDSP correctly targeted the sku-taro folders too, unlike Viper.
A bounty is basically you post a reward amount to any dev that can get Viper working on our SD S22U, it will at least get some experienced and knowledgeable people onboard trying to figure it out instead of us grasping at straws.
Click to expand...
Click to collapse
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.

ffp. said:
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
Click to expand...
Click to collapse
No idea tbh, I saw one guy post a bounty to get viper working on snapdragon s21 ultra, and it was claimed, but that was mostly it. I don't participate in these forums much so don't know about the specifics.
I have seen a few posts about snapdragon S21U with viper on one ui 4, but whatever methods they were using didn't work on s22u iirc, probably because those phones started with android 10, 11, whilst S22U is android 12 out of the box.

ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
All that you should need is root, your device set to permissive mode, install V4A and let it install the drivers when it prompts you the first time you open V4A(grant V4A superuser/root permissions).
Can you confirm that you are properly rooted with correct permissions and r/w properly set?
Can you confirm your device is actually in permissive mode?

I will add that you could also use Wavelet
Wavelet: headphone specific EQ - Apps on Google Play
Headphone specific equalization with lots of customizability
play.google.com
Made by the same developer whom made Viper4Android. There are reports saying It provides the same level of quality.

Droidriven said:
All that you should need is root, your device set to permissive mode, install V4A and let it install the drivers when it prompts you the first time you open V4A(grant V4A superuser/root permissions).
Can you confirm that you are properly rooted with correct permissions and r/w properly set?
Can you confirm your device is actually in permissive mode?
Click to expand...
Click to collapse
Yes, i have root, however S22U do not havr system rw. I can change things via magisk, though.
No, i didn't manage to get it to work. I'm using james dsp, which is pretty good if correctly set.

I had custom kernel (obligated, to have unofficial TWRP installed) with SElinux permissive mode permanently - V4A still did not work on my s22u model S908E (snapdragon; stock A12) - Kept getting driver install loop everytime I opened V4A app.
According to Dr. Ketan (see link message), V4A will not work on s22u Snapdragon models regardless of SElinux being permissive or enforcing.
Awaiting new development/ resurrection of this beloved sound Mod (s22u speakers suck, coming from a buttery smooth ROG-3).
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

Fytdyh said:
I will add that you could also use Wavelet
Wavelet: headphone specific EQ - Apps on Google Play
Headphone specific equalization with lots of customizability
play.google.com
Made by the same developer whom made Viper4Android. There are reports saying It provides the same level of quality.
Click to expand...
Click to collapse
they didnt make viper for Android. He had no part in the development of the so driver that makes the sound change. Viper520 did and I still dont understand why he walked away and has never came back. Dewitt just made some changes to the apk file. I can assure you he hasnt got a clue on how to make a sound driver. Technically james dsp is a so file sound driver that he did make.
I have a new tab s8 plus on one ui 4.1.1 right now and I can't believe viper wont work with a permissive kernel even. I like you guys got jamesdsp to work by installing as Huawei device and thought maybe that would correct the problem with viper and it didnt.
I do believe system RW would make the difference and I know the developer for the S8 tablet is working on making a twrp and a rw file that will work on that. I thought the s22 ultra was able to make RW now with the RW file. You would have to find the twrp tab s8, s8+, s8 ultra thread and go onto their telegram where DR. Keaton also hangs out and see if it works on the s22 ultra because its working on some devices. I was thinking s22 ultra and fold 4. I don't know how long until the tab s8 will have it and I hope you guys read this look into and try it and get viper4android working. So god speed

James dsp installs a lib64 driver into the system when you use Huawei setting. Normally the sound driver installs in the lib folder instead. I dont think its possible with viper
Huawei install
/data/adb/modules/ainur_jamesdsp/system/vendor/lib64/soundfx/libjamesdsp.so
Normal install
/data/adb/modules/ainur_jamesdsp/system/vendor/lib/soundfx/libjamesdsp.so
I do believe system RW will allow viper to work

Im almost 95 percent sure s
ffp. said:
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
Click to expand...
Click to collapse
Have you made your system read/write yet? Im 95 percent certain that the problem. Im on android 13 on my poco f3 and now viper wont install and it says Error Could not mount system read write s22 ultra is able to be rw with Dr. Keaton's stuf I believe

It worked?

amar100 said:
It worked?
Click to expand...
Click to collapse
I couldn't figure it out you want to try mine?

amar100 said:
It worked?
Click to expand...
Click to collapse
What device do you have any details please

ScarletWizard said:
The 64 bit version of viper has been released. If you're on Android 13 on a 74 bit soc. You gonna need the new v4a 64
Click to expand...
Click to collapse
What are you talking about? Where's the 64bit version

Yes
Techguy777 said:
I couldn't figure it out you want to try mine?
Click to expand...
Click to collapse
Yes Pls

Question Is there anyway to run 32 bit apps?

I don't know if this is the right place to ask or if it already has been or not, but is there any possible way to get 32 bit apps to run in some type of compatibility mode or something like that? For the most part the majority of my old apps came over from my old phone, however there are some apps I have and used regularly which are not compatable with this phone and I am not sure if the developers are still active or not. I'm assuming the answer is no, or would require root if it were possible and rooting is out of the question for me because I have Verizon. I am expecting to be SOL but figured it was worth asking about here.

This question has been asked and discussed in length, try search

I will not be rude and the short answer is no. Apps on the play store had roughly 2 years to switch 64 bit. For s**ts and giggles I did try to do a search with zero results.

If the devs are still active and they havn't updated to 64bit by now then they are a lost cause.

No Google's heads up to devs gave them ample amounts of time to switch all their apps from 32bit over to 64bit. Tough shiz if the devs didn't take the arning seriously and switched their apps over whenthey had the cance to do so. I'm genuinely curious of 32bit compatibility is a concern and/or a necessity for you why you would buy a smartphone that doesn't support it? I really don't see how that makes much sense when you could have chose from a lot of other new flagships with 32bit support in tact.

Get a Galaxy S22 Ultra, Motorola Edge 30 Ultra or OnePlus 10 Pro. It's likely next year's flagships of any brand will be 64 bit only, so the forced shift is coming.

I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there would be a way around it but obviously not.

This might be of some help to run 32 bit apps you want:
GitHub - ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com

Interesting I will have to check this out

Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo.

VergeDX said:
Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo
Click to expand...
Click to collapse
Remove "stock' magisk
Install the patched magisk apk
Patch the stock init boot with the patched magisk apk
Flash the new patched init boot

on a clean install it works for me (beta: cheetah-t1b3.221003.008)

lunacies said:
I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there wld be a way around it but obvio
Click to expand...
Click to collapse
That's what I meant by and or sorry if me misinterpreting what you meant

bhammler said:
on a clean install it works for me (beta: cheetah-t1b3.221003.008)
Click to expand...
Click to collapse
I've compiled Magisk with the supplied patch from the repo and it isn't working for me. I've verified that the init does include the changes to override ro.zygote, however none of the Zygote processes start as the adb server never starts up, and well it doesn't boot.
Tested with the modified Magisk APK from the repo, same deal.
Strange that a clean install is necessary.

don't bother with a clean install, after I've installed some Mgaisk modules, I had a bootloop ;-)

It's nice to see there may be an option and I hope it works for everyone else. I am stuck with a Verizon phone so rooting is out of the question for me and I figured something like this would require root but hopefully other people are successful in getting it to work.

This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.

Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com

hahimot483 said:
Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
No as I discuss here.
Namelesswonder said:
Didn't sleep, I have gotten closer, but Magisk modules aren't going to be the solution.
The earliest Magisk allows you to modify properties is after the post-fs-data trigger, which is well inside the init.rc. This is problematic because the property needs to be set before init.rc is even read.
Using a Magisk module to replace the init.rc with something else also isn't possible, since Magisk doesn't setup the overlays until well into the boot process.
This replacing is necessary because init.zygote64_32.rc actually has the secondary zygote service disabled, so the file needs to be modified to enable it, or with control over init.rc just stuffing a custom zygote service into it.
I don't think slipstreaming a modified init.rc and init.zygote64_32.rc into the ramdisk in init_boot will work since they would be overwritten once the system partition mounts. Could just modify the system partition, but that'll be for another day.
Click to expand...
Click to collapse
Gerr1 said:
This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.
Click to expand...
Click to collapse
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.

Namelesswonder said:
No as I discuss here.
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.
Click to expand...
Click to collapse
Yes it works now with the new magisk Manager APK.

Database Info

welcome