Related
I tried to word the title correctly to establish that I want to ask 2 different questions, but dont want to clutter up the board with 2 separate posts
Please help if you can
1. Kernel
Why do some kernels work with some roms and not others? I have taken a Sprint Rom, ran it through the kitchen, and tried flashing any number of kernels. The only one that works is Zenulators AnyKernel. I know at times only the stock overclocked worked, but I think at certain times I have gotten the no perf lock to work (though that may have been with an NFX Rom, and not one that I created myself). This leads me to ask why would a kernel work for a rom that is built from the same base that I am using, but not on mine? Is dsixda's kitchen not the one everyone uses? I just dont understand why I am limited to one kernel that is not undervolted and overclocked. I would like to put a 768 overclocked, undervolted kernel with this rom, but cant get any to flash. Should I just use the kitchen to "port" the kernel. How does nfinitefx45 get the kernels he posts to work with a Sprint base? Is the kernel edited in some way? Im not calling anyone out, just trying to learn how to get a good kernel to work with my rom.
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
I decided to take another cracked at a minimal Sprint 2.1 Rom. I used dsixda kitchen 0.107 to root, add busybox, remove boot sounds, deodex, add data/app, add nano + sysrw, sysro, bash, and zipalign the .7 Rom. I then removed all Sprint apps except for VVM, all google apps, all htc apps and widgets that were not explicity needed (need the contacts and ime apks among a few others), removed a ton of system apps (can provide a list of current system/app dir and a list of all that was removed if it will help). I edited the lockscreen so it wasnt in landscape mode all the time. Added an OMADM.apk file that didnt FC when I tried to update the prl (tested the update and it works). I did find an EPST.apk that adds ## codes back to the dialer (should I include that in the rom...wasnt intending on it as the only ## code that doesnt work is the prl...data works) OMADM.apk is smaller that the EPST...but EPST does exist already...and I might be able to pull OMADM meaning 0 firmware, profile, or prl updates...but you could do ##prl manual...I dont know, still thinking it through. I did end up creating a google apps zip file with the apps from the .7 rom so that market will work (removed maps as it wasnt up to date and the Streets.apk never worked, but left gmail, youtube, voice search to work with jonasl's htc keyboard, and of course gtalk). In doing this, I am thinking about creating some packs for the rom, but really need the above 2 questions answered to find out where to go from here.
evilvoice said:
1. Why do some kernels work with some roms and not others?
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
Click to expand...
Click to collapse
afaict, the 'kernels' are literally just the linux kernel that provides some basics to the os... altho linux IS a monolithic kernel, it is not a bsd-system that has all the tools completely-compiled for the system together...
thus, the answer to 2. is that you have deleted too much of the periphery, for instance the actual mount-table system that df uses to to check... (ie: some prog creates the mtab, and apparently it is not the kernel, i guess)
alternatively, the answer to 1. is that there is actually too much in the roms that are using something unique to each kernel that you are trying to install (altho that seems odd to me)... thus, the only way that the rom will work is if you give it the kernel with the tools that it (the rom) needs...
tbh - im not exactly sure - ive not gone into the depths of kernel-swapping that youre trying to explore... in full-linux-systems, the kernel is fairly easy to update without breaking all of the miscellaneous tools - however apparently the android-roms are more tied-together than a normal linux system...
gl and maybe someone with more experience will give an accurate (rather than a guessing) answer...
deleted .
Finally ! That bug was very annoying to me.
I'll try the fix asap, thanks a lot!
e: works like a charm!
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
j4n87 said:
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
Click to expand...
Click to collapse
Because you posted it in the "Themes and Apps" section
thanks a lot for post here
great job
kackburt said:
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
Click to expand...
Click to collapse
you mean copy the actual zip file into the ROM zip and then flash?
jonny68 said:
you mean copy the actual zip file into the ROM zip and then flash?
Click to expand...
Click to collapse
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Tried on UD3.3.0 wont boot... :s
People dont understand that this work the best on CM7 nexus roms.
That by installing this fix on CM7 or AOSP you will probaly lose the robo and high volume on first call fix. That most roms have custom libs including this lib. Minimum requirements I would say CM7 2.34 and AOSP 2.34 since cm7 and AOSP are the most equal roms to each other.
To say it simple you cant just simply flash this on every rom also make sure your permission is right.
Is this fix able to work on an HTC Desire running 2.3.4 Oxygen ROM?
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
If you have a nandroid backup, you should be on the safe side!
Try to wipe cache partition first, then the dalvik cache and then flash the zip-file.
All of these actions take place in the CWM.
Hope it works!
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
jens1288 said:
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
Click to expand...
Click to collapse
Yes, that fix works fine. I'm not sure it fixes the few seconds delay that affects all Gingerbread phones though but there was another potential workaround submitted for that too.
http://review.cyanogenmod.com/#change,5420
I have yet to include it in my build and try it though.
The story on the front page links to the wrong fix. The libaudio fix was for the wonk on the Nexus One. The libaudio library is hardware specific and may cause issues on other devices that don't share the same processor.
I've submitted a patch to gerrit that helps with the call delay here:
http://review.cyanogenmod.com/#change,5420
Thank you for clearing that up jyxent. To go into a bit more detail...
The fix that was posted, as jyxent mentioned, is for the Nexus One. That is for the infamous "wonk" that has been plaguing N1 users since the Gingerbread nightlies started (who woulda thunk it was just a single line that needed to be added).
The 2-3 second delay is something that affects most (if not all) Gingerbread installs. Currently there isn't a simple "fix" for this. It requires recompiling portions of Gingerbread. jyxent's fix is submitted to CM, but I don't see any reason why this can't be applied to AOSP as well. It has yet to be reviewed by the CM dev team (at least it doesn't have any comments on it yet). It might be something that can be made into some device-independent flashable zip, but it has yet to be created.
j4n87 said:
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Click to expand...
Click to collapse
done thanks
Can this be done manually with root explorer, by copying the libaudio.so to/system/lib and a reboot?
This is meant to be a guide for people interested in building AOSP based roms and is strictly for developers only. If you wish to have gesture typing in your rom the most simple way is to include/install "LatinImeGoogle.apk".
Not everyone wants to always use google's stock input apk, particularly if you have made modifications into AOSP latinime keyboard if your own and want it to propagate through to your roms without sacrificing gesture input (which i have found is quite useful). Well after some digging around there's good news and bad news.
The good news is that the gesture typing is already in the source tree on the java side and can be enabled by changing packages/inputmethods/LatinIME/java/res/values/gesture-input.xml or using the overlay in devices/../mako (not within scope of this post).
Code:
<bool name="config_gesture_input_enabled_by_build_config">true</bool>
However, just changing the value you will notice that it will draw the gesture but list no words. Thats because google didnt include the "gesture decoder" in the AOSP sources because it is super secret. You can see the code stubs in the C++ part of latinime under native/jni/src/gesture/* .
As a result, libjni_latinime.so will not contain code to decode the gestures and will not read from the dictionary.
BUT! There is a way! You can drop in replace the lib from "LatinImeGoogle.apk" into your system/lib and you will have your gesture decoder!
The library inside the apk is called "libjni_latinimegoogle.so" under /lib/<arch_type>/ inside the apk. You can extract this library from within android using program like root explorer and on PC using android apktool (http://code.google.com/p/android-apktool/). Rename this shared library to "libjni_latinime.so" to replace the AOSP built one and it will decode the gestures through the AOSP based keyboard.
Enjoy!
-removed-
Thanks for sharing the detailed instructions. This was a major annoyance..
kabir_sharma009 said:
Thanks for sharing the detailed instructions. This was a major annoyance..
Click to expand...
Click to collapse
I see you too have recently had an issue with this. I've followed everything, even using different sources for the libjni_latinimegoogle.so (noticed varing sizes) but none of them have worked for me. I installed the apk out of CM10.2.1, and the gesture trail shows up but still no library it seems. Any idea what I might have missed? Renamed file as directed and put in in the system\lib folder.
Thanks in advance for any help you may have to offer.
Edit:
Got it. Restart the phone...I feel like I should have called tech support
Re-Edit:
Negative, didn't realize at first it was set to Samsung Keyboard...Help still needed.
TheLastRebel1123 said:
I see you too have recently had an issue with this. I've followed everything, even using different sources for the libjni_latinimegoogle.so (noticed varing sizes) but none of them have worked for me. I installed the apk out of CM10.2.1, and the gesture trail shows up but still no library it seems. Any idea what I might have missed? Renamed file as directed and put in in the system\lib folder.
Thanks in advance for any help you may have to offer.
Edit:
Got it. Restart the phone...I feel like I should have called tech support
Re-Edit:
Negative, didn't realize at first it was set to Samsung Keyboard...Help still needed.
Click to expand...
Click to collapse
I've attached the file in .rar format for you, extract the .so file from the archive using WinRAR and replace the existing file in System/Lib with this one.
You might get an error while trying to replace the file if AOSP Keyboard is selected as default input method, so switch to another keyboard before replacing the file (Swype Keyboard Trial is what I used).
Thanks for getting back to me. Unfortunately it additional didn't work. Any other ideas?
kabir_sharma009 said:
I've attached the file in .rar format for you, extract the .so file from the archive using WinRAR and replace the existing file in System/Lib with this one.
You might get an error while trying to replace the file if AOSP Keyboard is selected as default input method, so switch to another keyboard before replacing the file (Swype Keyboard Trial is what I used).
Click to expand...
Click to collapse
Works perfectly for me. Thanks a lot!
Fantastic trick. Worked on my wife's S3 mini running MacClaw's latest KitKat. Thanks so much for this.
Didn't work for me, AOSP keyboard just FCs
not much of a difference between aosp & google keyboard
Sorry I thought I was on a different thread
How I got gestures working on cm11
So, I'm uncertain if this is exactly what this thread is about, but it might help someone.
Some backstory:
I had cm11 for a long time with a working Android AOSP keyboard.
After trying cm12.1 for a while I went back to cm11 with a fresh install, and noticed my gestures not doing much, and causing the FC.
I did a lot of searching, but nothing seemed to fix my problem, including the suggestions from this thread.
Since I had a nandroid of my previous installation, I did some comparisons, and came across the file libjni_unbundled_latinimegoogle.so in the /system/lib.
Copying this to my new installation fixed gesture typing for me. So now I share my solution to whoever can use it.
I hope this helps someone!
FreakyJoost said:
So, I'm uncertain if this is exactly what this thread is about, but it might help someone.
Some backstory:
I had cm11 for a long time with a working Android AOSP keyboard.
After trying cm12.1 for a while I went back to cm11 with a fresh install, and noticed my gestures not doing much, and causing the FC.
I did a lot of searching, but nothing seemed to fix my problem, including the suggestions from this thread.
Since I had a nandroid of my previous installation, I did some comparisons, and came across the file libjni_unbundled_latinimegoogle.so in the /system/lib.
Copying this to my new installation fixed gesture typing for me. So now I share my solution to whoever can use it.
I hope this helps someone!
Click to expand...
Click to collapse
Did you mean copying that lib file in location mentioned by you alone should give gesture typing ability? Because it didnt work on my zenfone with custom rom, blisspop 6.0.1
harpy.eagle said:
Did you mean copying that lib file in location mentioned by you alone should give gesture typing ability? Because it didnt work on my zenfone with custom rom, blisspop 6.0.1
Click to expand...
Click to collapse
In my situation it did, bat as mentioned I use cm11. Seems however the name is kind of related to the build of the apk. Apparently this was the same file as the one mentioned before, just with a different name.
You could try finding an older version of suitable gapps that provides a libjni_latinime.so and see if that one works...
I was able to enable gesture typing on a fresh install of CM13 without installing Gapps by extracting the file libjni_unbundled_latinimegoogle.so from the keyboard apk in openGapps for android6 (the "stock" version includes google keyboard). I placed the file in the /system/lib folder. Only difference is that I renamed that file to libjni_latinimegoogle.so . All was left was to soft reboot and enable gesture typing!
forgot to mention I set permission to -rw-r--r--
Hi all.
Noob here on the forum, my very first post so i am not allowed to post this where i imagine this would belong - the 'Original Android development'. That's why it is posted here.
First of all, i wish to express my sincere gratitude to all you people that work hard on making it possible for rest of us mortals to make the best of those small devices that somehow managed to become so big parts of our lives.. I have been following the forum for a while and been using some things posted here to fiddle with several devices without actually bricking any of them as yet. And this is the first time i felt the need of actually asking for help and/or guidelines.
Anyhew - here's the thing: i still run a N910F on stock marshmallow as my main device. (Please no lectures about this). And lately i came to really, really resent mr.Google. I did make a Lineage version of the Android Pie work together with microG (without google), and that actually is rather sweet, runs smooth as silk. I run that on my backup N910F device. (Ok, so i am a Note 4 freek, sue me).
But for different reasons, actually mainly because i really appreciate the s-pen, i want to continue using stock rom on my daily driver so now i am looking for a google-free version of the stock marshmallow for the N910F (trlte) model. I tried to find it here on the forum, but i couldn't, or i couldn't understand the terminology. Haven't found in the rest of the internet either. So i would appreciate if somebody here could either:
1. point me to the direction of such a version if it's already existing, or
2. give me very specific information as to how i could de-google the stock rom by myself. Either on the device or in Windows. I haven't used adb or fastboot yet, but perhaps i could learn if i don't have to take a class in engineering first…
Or could i simply use Titanium backup and just delete (freeze first of course) all the apps that have 'google' in their name?
The third option is perhaps that some kind sould de-googles the stock rom for me and lets me download it. I would donate, of course.
I would really appreciate all the pointers you could give me.
Regards,
prkfsz
Nope, the N910F stock firmwares are definitely not de-Googled. Flash one for yourself and see. I would recommend flashing a LineageOS/AOSP-based ROM, they are generally Google-free.
If you are really insistent on running stock, then do this to completely de-Google it:
In Titanium backup, search for 'goo', this will find almost all Google apps on the ROM. Uninstall them.
Also, download the latest OpenGapps ARM 6.0 nano zip from opengapps.org. Extract the gapps-remove.txt file from the zip. Use the contents of that file as a reference, find all the files listed in it, manually delete them. The reason for this is that Titanium will miss some things.
Now you should be mostly if not entirely Google-free.
Once you have done that, you can optionally patch your ROM for signature spoofing support, and install MicroG, which is an open source Google Play Services alternative. These 2 steps are optional, your choice.
Very simple. I've done this before, things will work fine overall. But some things (apps) requiring Google components may not work correctly, if at all. MicroG can help mitigate this to an extent. You've been warned.
I'm running Resurrection Remix Nougat v5.8.5 (Android 7.1.2), SPen works fine here. Every app I've tested that can use the pen, works fine. There is really no reason to stay with stock just for pen functionality. I also like the huge amount of customization options that RR has compared to stock. And I can use Substratum (no go on stock) with all black themes, for battery savings.
Thank you! Wasn't aware of the google-remove.txt file within gapps. Will definitelly use it. Otherwise it's like i thought: use Titanium and just go loose on everything that starts with 'go'...
I know about microG and use it regularly. Happy customer…
I do like stock marshmallow on note 4 and want to run it as long as it can go. I will perhaps try the RR nougat you suggested on the backup unit. Even tho i am in no particular need of customisation.
Thanx again.
prkfsz said:
Thank you! Wasn't aware of the google-remove.txt file within gapps. Will definitelly use it. Otherwise it's like i thought: use Titanium and just go loose on everything that starts with 'go'...
I know about microG and use it regularly. Happy customer…
I do like stock marshmallow on note 4 and want to run it as long as it can go. I will perhaps try the RR nougat you suggested on the backup unit. Even tho i am in no particular need of customisation.
Thanx again.
Click to expand...
Click to collapse
You might find this of some interest.
https://forum.xda-developers.com/android/general/guide-degoogle-device-install-microg-t4058743
I'm afraid i got stuck here and i need a bit further assistance.. :-/
Coming from stock marshmallow on Galaxy Note 4. I uninstalled google things first using Titanium. Then manually cleaned some leftovers using file manager in TWRP (not sure i did the right way), altho it looked quite empty in the /system map. Another time erased just the Google Play-services before going to TWRPs file manager and it looked just as empty. At both occasions i lost auto-rotate. Is this normal?
After deleting all the google (and in the second try only google play services app) i tried just for the heck of it to run the Nanodroid patch file but i got an error message that it couldnt deodex services.jar file, which was pretty much expected. My skills are not sufficient for deodexing files so i tried other approaches for patching. Smalipatcher - the damn thing couldn't even see i had admin privileges in Win no matter what i did and just refused to run alltogether.
Then i tried the link that was put here by @MrJavi in the post above (thank you sir!). Did everything as the tutorial says, got no error message, everything seemed to run smooth and the apps i chose were installed. (altho TWRP did freeze a couple of times during aroma setup so i had to reset by taking out the battery). When i wanted to set up the microG settings, the microG icon and the app is nowhere to be found. The modul named NanoDroid exists and is activ in Magisk, but it's not possible to open it.
Last, but not least of course, i tryied patching with fake gapps module in Xposed, but Xposed of course does not want to play nice with mr.Samsung. Even when i try and run Xposed from Magisk...
Not sure how to proceed from here.. I'm thinking of switching my starting point to the already deodexed version of marshmallow i thought i saw around here, because it would be easier to patch.
If it's still out there available for download, which i don't take for granted anymore nowadays..
But i would like to make it work on my device anyway. So, if anyone has any ideas, they will be so welcome.
Perhaps Samsung knox is causing issues with Xposed framework/installer. The link below is for a different "Samy" but the the Knox remover is a flashablw .zip made specifically for the Note 4 .
https://www.google.com/amp/s/forum....-how-to-deodex-root-remove-knox-t3458921/amp/
https://www.google.com/amp/s/forum....al/toad-source-android-deodexer-t3848307/amp/
Always take a full Nandroid backup by checking all partition beforehand and save to your external sd card. You can then choose to flaah an Aroma Google debloater .zip .
https://forum.xda-developers.com/android/software-hacking/aroma-google-services-debloater-t3668456
Mr. JAVI said:
Perhaps Samsung knox is causing issues with Xposed framework/installer. The link below is for a different "Samy" but the the Knox remover is a flashablw .zip made specifically for the Note 4 .
https://www.google.com/amp/s/forum....-how-to-deodex-root-remove-knox-t3458921/amp/
https://www.google.com/amp/s/forum....al/toad-source-android-deodexer-t3848307/amp/
Always take a full Nandroid backup by checking all partition beforehand and save to your external sd card. You can then choose to flaah an Aroma Google debloater .zip .
https://forum.xda-developers.com/android/software-hacking/aroma-google-services-debloater-t3668456
Click to expand...
Click to collapse
wow, those were really some good links! thanks, @mr.javi. However....
tried the first link and to work with firmware but the ext4uninstaller does not want to recognize the ext4 file (wtf??), regardless from where i download the software and regardless what ext4 file and from what firmware (tested a few), and without that part working it was pretty much impossible to go on. So i ran only the deknoxing tool through twrp. No error. But still when i try and install the xposed - boom! it will not boot. Not even damn zip uninstaller for magisk will work as it should..
Tried the second link with the TOAD. Weird: some versions get recognized as malware by my antivirus and windows does not want to run other versions for safety reasons. Strange..
Tried the third and that de-googling script is rather sweet.
But my conclusion from all this is that it is not so hard to exorcise the google, but to patch the rom in the next step... If i understand correctly i have to get the rom deodexed first to be able to patch it with nanodroid?
I tried some deodexing tools on pc, but i'm not really sure if i'm doing it correctly. I take it i have to copy some folders (/apps, /framework and one more) from the phone to the computer to work with them there, but i get error message when i try to copy files through file manager in twrp. Am i supposed to do it some other way? And can you do that directly in the phone? I tried an app called 3c -all in one-toolbox that has native option of deodexing but i get error message there, something about classes i think, i don't remember and i can't see it now cause the phone is just being reflashed..
Any more thoughts and ideas? As usual, grateful for anything you can give me.
AnonVendetta said:
Once you have done that, you can optionally patch your ROM for signature spoofing support, and install MicroG, which is an open source Google Play Services alternative. These 2 steps are optional, your choice.
Very simple. I've done this before, things will work fine overall. But some things (apps) requiring Google components may not work correctly, if at all. MicroG can help mitigate this to an extent. You've been warned.
Click to expand...
Click to collapse
HOW?! did you manage to patch it??
prkfsz said:
wow, those were really some good links! thanks, @mr.javi. However....
tried the first link and to work with firmware but the ext4uninstaller does not want to recognize the ext4 file (wtf??), regardless from where i download the software and regardless what ext4 file and from what firmware (tested a few), and without that part working it was pretty much impossible to go on. So i ran only the deknoxing tool through twrp. No error. But still when i try and install the xposed - boom! it will not boot. Not even damn zip uninstaller for magisk will work as it should..
Tried the second link with the TOAD. Weird: some versions get recognized as malware by my antivirus and windows does not want to run other versions for safety reasons. Strange..
Tried the third and that de-googling script is rather sweet.
But my conclusion from all this is that it is not so hard to exorcise the google, but to patch the rom in the next step... If i understand correctly i have to get the rom deodexed first to be able to patch it with nanodroid?
I tried some deodexing tools on pc, but i'm not really sure if i'm doing it correctly. I take it i have to copy some folders (/apps, /framework and one more) from the phone to the computer to work with them there, but i get error message when i try to copy files through file manager in twrp. Am i supposed to do it some other way? And can you do that directly in the phone? I tried an app called 3c -all in one-toolbox that has native option of deodexing but i get error message there, something about classes i think, i don't remember and i can't see it now cause the phone is just being reflashed..
Any more thoughts and ideas? As usual, grateful for anything you can give me.
Click to expand...
Click to collapse
You're very welcome @prkfsz
https://mtkcustomroms.com/deodex-stock-rom-custom-rom-without-pc-2018/
https://how-to-easily-deodex-android-stock-rom-without-pc/
Mr. JAVI said:
You're very welcome @prkfsz
https://mtkcustomroms.com/deodex-stock-rom-custom-rom-without-pc-2018/
https://************/how-to-easily-deodex-android-stock-rom-without-pc/
Click to expand...
Click to collapse
Thanx again, @Mr. JAVI! :good:
Both links are about the same app and i've tried that one recently, so it seems like we think rather alike.
I get the exact same error message like the guy that wrote that one comment at the bottom of the second link (error saying "needs rebuild classes.dex").
And strangely enough when i open the deodexing window in the app it says that of the number of apps in the rom not all are odexed (says something like "deodexed 124/187"), which is rather perplexing because it's on the freshly installed stock (from nandroid backup directly after factory reset). So I tried to fool the app and get all the apps odexed first, but that didn't fly either..
Btw, thanks for the advice before - i always back the device upp (all partitions) before messing with it.. I forgot to do that on one device before and instantly regretted it..
-------------------------------------------
Edit: the second link in your last post was dead so i tried to correct it in my message, but xda forum doesn't like that.
Tried to post in the right link here in the message too, but that didn't work either for some reason.
but searching the phrase 'how to easily deodex Android stock rom without pc' will give you the first search result.
Oat2dex.jar
https://www.google.com/amp/s/forum....eral/tool-deodex-tool-android-l-t2972025/amp/
https://github.com/testwhat/SmaliEx/releases
---------- Post added at 01:14 PM ---------- Previous post was at 12:43 PM ----------
prkfsz said:
Thanx again, @Mr. JAVI! :good:
Both links are about the same app and i've tried that one recently, so it seems like we think rather alike.
I get the exact same error message like the guy that wrote that one comment at the bottom of the second link (error saying "needs rebuild classes.dex").
And strangely enough when i open the deodexing window in the app it says that of the number of apps in the rom not all are odexed (says something like "deodexed 124/187"), which is rather perplexing because it's on the freshly installed stock (from nandroid backup directly after factory reset). So I tried to fool the app and get all the apps odexed first, but that didn't fly either..
Btw, thanks for the advice before - i always back the device upp (all partitions) before messing with it.. I forgot to do that on one device before and instantly regretted it..
-------------------------------------------
Edit: the second link in your last post was dead so i tried to correct it in my message, but xda forum doesn't like that.
Tried to post in the right link here in the message too, but that didn't work either for some reason.
but searching the phrase 'how to easily deodex Android stock rom without pc' will give you the first search result.
Click to expand...
Click to collapse
Well to tell you the truth, even a full Nandroid backup couldn't fix a dm-verity/drk issue on one of my Note 4's. Up until then I have always recovered from softbricking my devices. Stubborn as I am, I spent hours and hours and hours o no avail. I connected my other N4 but still kept trying to revive my old N4. It wasn't until a year and a half later, assisting another member that I came across a possible solution and it worked. Spent more time than my old N4 was worth but my record is untarnished non the less. lol I sure hope you never ever encounter either of thoughts @prkfsz .
Mr. JAVI said:
Oat2dex.jar
https://www.google.com/amp/s/forum....eral/tool-deodex-tool-android-l-t2972025/amp/
https://github.com/testwhat/SmaliEx/releases
---------- Post added at 01:14 PM ---------- Previous post was at 12:43 PM ----------
Well to tell you the truth, even a full Nandroid backup couldn't fix a dm-verity/drk issue on one of my Note 4's. Up until then I have always recovered from softbricking my devices. Stubborn as I am, I spent hours and hours and hours o no avail. I connected my other N4 but still kept trying to revive my old N4. It wasn't until a year and a half later, assisting another member that I came across a possible solution and it worked. Spent more time than my old N4 was worth but my record is untarnished non the less. lol I sure hope you never ever encounter either of thoughts @prkfsz .
Click to expand...
Click to collapse
And i thought i was stubborn for this, insisting on tweaking an age-old os and spending hours on looking for solutions.. thank you!
Not sure about what that issue you mentioned was, since i'm not really on that experience level, but i'm sure it was a mean one.. lol Good job of fixing it! I ended up a few times in similar situations (not with that high level issues apparently) and i just couldn't let go untill i resolved them or bricked them completelly... Luckily haven't bricked anything even tho i play mostly with older devices so it wouldn't be such a waste. But as you too apparently feel - unblemished record is a matter of pride..
And yes, i too recently understood that nandroid backup isn't allmighty - it can't for instance save certain safety settings, fingerprints and such. I always thought of nandroid backup like a 'clone' feature on PC. Loved that..
Aanyhew - back to business.
I hit the wall here again, the same one as with Fulmics deodexer. It's not that it isn't working, it's that i don't know how to point it to the right maps for deodexing.
As far as i understand, i have to copy those 3 folders from the phone to the PC, do the deodexing on the pc, and then move back to the phone and replace the original folders. Is this correct? I tried doing this in TWRPs file manager using micro sd card, but i gott error message that it wouldn't copy all the files for some reason. Should i use some other method of copying those folders to the PC?
Perhaps a stupid question but is there any way to let the deodexer on the pc find the folders directly on the phone?
As always - a huge thank you from the struggling noob, @Mr. JAVI. :good:
Perhaps this is the Xposed framework and installer that might be compatible with your N910f
https://forum.xda-developers.com/note-4/themes-apps/unofficial-xposed-v87-3-magisk-v18-t3897017/amp/
As far as TWRP you might be able to patch it and save internal data with Tipatch apk. The drawback is you backups will be much larger.
https://www.google.com/amp/s/forum....pp-twrp-tipatch-backup-internal-t3831217/amp/
PS: Thsnks for the compliment my friend but I'm still learning. Modifications is just a hobby of mine. We learn from each other here on XDA.
PC : skills are not my strong point . Your skills with PC far
exceed your ability. I actually bought a laptop years ago, just so I could flash TWRP Odin and root . The complete ssd laptop cost alot more than my Note 4. I port or create my own flashable .zips. Although, I've never been faced with having to deodex a custom rom, simply because there readily available from the developers on xda for the n910p. Sucks there hasn't been one developed for your n910f.
Something posted by @IBNobody
"Anything past Magisk v15.3 will not pass SafetyNet on QI5.*
Magisk v15.4+ added a check in its Magiskhide subsystem that looks a service (logd) to be loaded. That service is not running on our stock or slightly modified QI5 build. If this service check fails, Magiskhide does not get loaded. If Magiskhide is not running, it can't hide Magisk from the SafetyNet checks.
(You'll know if this is affecting you because the Magisk Manager app won't remember any settings you make in the Magisk Hide tab.)*
Our only options are:
1. Build our own fork of Magisk that skips this check.
2. Enable logd by modifying the init.rc file in boot.img. (logd is commented out. I have not tried un-commenting it.)
3. Remain on v15.3."
DQ15 is the Sprint firmware 6.0.1 and not n910f but it could be the same with yours as well.
A slightly lower version Xpoaed framework api 23
https://androidfilehost.com/?fid=529152257862685344
Mr. JAVI said:
Perhaps this is the Xposed framework and installer that might be compatible with your N910f
https://forum.xda-developers.com/note-4/themes-apps/unofficial-xposed-v87-3-magisk-v18-t3897017/amp/
As far as TWRP you might be able to patch it and save internal data with Tipatch apk. The drawback is you backups will be much larger.
https://www.google.com/amp/s/forum....pp-twrp-tipatch-backup-internal-t3831217/amp/
PS: Thsnks for the compliment my friend but I'm still learning. Modifications is just a hobby of mine. We learn from each other here on XDA.
PC : skills are not my strong point . Your skills with PC far
exceed your ability. I actually bought a laptop years ago, just so I could flash TWRP Odin and root . The complete ssd laptop cost alot more than my Note 4. I port or create my own flashable .zips. Although, I've never been faced with having to deodex a custom rom, simply because there readily available from the developers on xda for the n910p. Sucks there hasn't been one developed for your n910f.
Click to expand...
Click to collapse
Laptop cost way over Note 4? I see i'm not the only one..... ehh, let's say determined bloke around here haha.. Hope it was worth it.. And btw creating your own flashable zips is way above my level of skills, i can tell you that, my friend. Never did that, nor am i planning to. But since i am stubborn (or so i've heard.. lol) and i feel uttermost distaste for mrGoogle and, like you said, noone has apparently done the deodexing the stock N910F - I am simply forced to take matters into my own hands. Flashing a pie and microG is ... apparently too easy. Besides, i am already running that on one of my spare Note 4s.. And i appreciate xda, just like you say people can give each other a hand. What i dislike tho is lots of dead download links... Oh, well..
ok, back to business again.
I guess i am going to need a more detailed help now.
I tried with that version of Framework you linked to. At that page the link for Xposed installer app for Magisk is dead. Tried to play a little with the other file, the version 87.3 of Xposed and just flashed it in TWRP, but nothing happens.
As far as the Tipatch, excuse my ignorance but i have to ask here: what difference would it make for deodexing to be able to copy internal storage? I am thinking it's other folders that need to be copied, like /system.
Apart from that, i love the idea of Tipatch! Will install it anyway.
--------------------------------------------------------
I am beginning to realize that there are not many reasonable options left, since i'm not sure it is worth much more time and effort on my part. I am not going to be an engineer over this..
So there is but one more question to perhaps get solved before i run out of options and go with custom Pie anyway.
And that is - how do i copy the needed 3 folders intact to PC for deodexing software? I can't find that information anywhere together with this pc based deodexers.
Oh well. I have vague memory of ES file manager being mentioned somewhere. So i guess that will be my last attempt before i give up. Unless some new solution emerges.
Mr. JAVI said:
Something posted by @IBNobody
"Anything past Magisk v15.3 will not pass SafetyNet on QI5.*
Magisk v15.4+ added a check in its Magiskhide subsystem that looks a service (logd) to be loaded. That service is not running on our stock or slightly modified QI5 build. If this service check fails, Magiskhide does not get loaded. If Magiskhide is not running, it can't hide Magisk from the SafetyNet checks.
(You'll know if this is affecting you because the Magisk Manager app won't remember any settings you make in the Magisk Hide tab.)*
Our only options are:
1. Build our own fork of Magisk that skips this check.
2. Enable logd by modifying the init.rc file in boot.img. (logd is commented out. I have not tried un-commenting it.)
3. Remain on v15.3."
DQ15 is the Sprint firmware 6.0.1 and not n910f but it could be the same with yours as well.
A slightly lower version Xpoaed framework api 23
https://androidfilehost.com/?fid=529152257862685344
Click to expand...
Click to collapse
Ok, i managed to actually copy the system directory from the phone to the pc using Root explorer app. And none of the deodexers work. Fulmics says it needs smali and baksmali versions over 2.2 even tho i fed it with versions 2.4. SVADeodexerforart runs through all the files without actually doing anything. Logfile shows error 'cannot acces jar file' on all 300+ files.
So i believe this is it for me at this point. I just can't see how further struggle would be meaningsfull since it would just take even more time and i already invested way too much of it on this. But i guess being stubborn has it's price.. :silly:
I want to extend my sincere gratitude, @Mr. JAVI, for your patience, tips and guidelines. I think if it wasn't for you i would given up much quicker.. Which perhaps would've been a smart thing to do... But i wouldn't learn anything..
We will probably bump into each other more times here, since we seem to share the common affection towards a certain gadget.
all the best to you
prkfsz said:
Ok, i managed to actually copy the system directory from the phone to the pc using Root explorer app. And none of the deodexers work. Fulmics says it needs smali and baksmali versions over 2.2 even tho i fed it with versions 2.4. SVADeodexerforart runs through all the files without actually doing anything. Logfile shows error 'cannot acces jar file' on all 300+ files.
So i believe this is it for me at this point. I just can't see how further struggle would be meaningsfull since it would just take even more time and i already invested way too much of it on this. But i guess being stubborn has it's price.. :silly:
I want to extend my sincere gratitude, @Mr. JAVI, for your patience, tips and guidelines. I think if it wasn't for you i would given up much quicker.. Which perhaps would've been a smart thing to do... But i wouldn't learn anything..
We will probably bump into each other more times here, since we seem to share the common affection towards a certain gadget.
all the best to you
Click to expand...
Click to collapse
I am just one of the "common folk". One of my hobbies is modifying my rooted Note 4. I have learned from my failures as well. The creating custom zips is not as hard as you think, in fact it was a failed camera .zip fash that ended in FC's. I came up with an idea to take the previous working camera .zip. left the meta-imf and replaced tge rest with an N7 camera from another rom and fkashed it. It's much easier explained with screen shots.
One of my favourite apps is ZArchiver apk. Downliad it and you'll see why. Ext4, tar, zip, roms, jar, apks and more. Freaking Awesome!!!
https://play.google.com/store/apps/...pk&pcampaignid=APPU_1_YUIBX4STE-aD9PwPh7ylmAg
Its like gold and did I mention free? lol
Welcome to XDA @prkfsz
Mr. JAVI said:
I am just one of the "common folk". One of my hobbies is modifying my rooted Note 4. I have learned from my failures as well. The creating custom zips is not as hard as you think, in fact it was a failed camera .zip fash that ended in FC's. I came up with an idea to take the previous working camera .zip. left the meta-imf and replaced tge rest with an N7 camera from another rom and fkashed it. It's much easier explained with screen shots.
One of my favourite apps is ZArchiver apk. Downliad it and you'll see why. Ext4, tar, zip, roms, jar, apks and more. Freaking Awesome!!!
https://play.google.com/store/apps/...pk&pcampaignid=APPU_1_YUIBX4STE-aD9PwPh7ylmAg
Its like gold and did I mention free? lol
Welcome to XDA @prkfsz
Click to expand...
Click to collapse
Why thank you good sir, @Mr. JAVI! :good:
Every noob should get this friendly a welcome..
See? All that meta-inf, FC-talk is a bit over my lever right now. But i will check out your tool. Might come in handy for some future project. And free it is you say? Sold! haha
As for this project i had, i had to abandon it for now. I realized it wasn't the degoogling that was the problem, but the patching afterwards, and the deodexing that turned out to be downright impossible to get done. And it just gotten too time-consuming in relation to how much time i actually have and how much win i would get out of it. So i took the easy way for now and i went with the custom Pie. I do want the audio from the headphones..
@prkfsz: I used Tingle patch to integrate signature spoofing. You have a few options:
Tingle patch (requires deodexed framework.jar)
Needle patch (requires deodexed framework.jar)
Nanodroid patcher (requires deodexed services.jar)
Haystack patch (requires deodexed services.jar)
Smali patcher (services.jar can be odexed or deodexed, it will deodex and patch the file for you)
FakeGApps (requires Xposed)
Options 1/2/4/5 require a PC. Options 3/6 can be done on device without PC.
Hope this helps!
I don't really have a lot of time to go into detail, but if either of you are looking for a comprehensive way to properly deodex a ROM, check out SuperR's Kitchen. There a free and paid/donate versions. The free version can do what you want just fine.
I had recently used this to deodex the latest stock MM UK firmware for the N910F. In addition to deodexing, the Kitchen can also customize your ROM, and even build a zip that you can flash in TWRP. It flashed and booted fine for me. Once you have done this, you can debloat the ROM (or let the Kitchen do it for you). It won't remove all Google stuff by default, but you can configure it to delete pretty much any file/directory in the system partition. My advice is to use the Kitchen's debloater/Knox removal features, then use gapps-remove.txt and a root file manager to delete the rest. Once you have debloated/deodexed, you can then easily signature spoof patch with any of the tools I mentioned in my previous post.
I have also discovered that you can also run the Tingle patch without a PC, by using QPython3 app. Just supply the deodexed framework.jar and build.prop, it will do the rest. Grab the Tingle master zip from GitHub, unpack it into QPython3's scripts directory on the internal storage, then provide the 2 files into input folder, and run main.py from within the app. You will find the patched jar file in output folder, replace your ROM's framework.jar with the patched one. Use Signature Spoofing Checker to confirm that it worked. I don't think root is required, but it's better to have it anyway, just enable root in QPython3 settings.
Some last notes: don't use Titanium to debloat Google apps, it may also remove some needed shared library files that Android uses. Namely, a library file called libgnustl_shared.so, which will cause autorotation to not work. Use Titanium to determine the locations of Google apps, then delete them manually. This will keep the shared library files while still deleting the apps. On top of this, use gapps-remove.txt.
But while you are debloating, there may be 2 Google apps present that you should not remove, period:
/system/app/WebViewGoogle
/system/priv-app/GooglePackageInstaller
The first is needed by Android and apps to provide webview functionality (this might not sound important, but it is). The 2nd is needed to install apps, remove it and you won't be able to install any app from anywhere (Play Store, manual APK install, etc).
On the subject of Xposed, do *NOT* install the Xposed installer from the Magisk Manager downloads. It isn't designed to work on stock Samsung MM firmware, you won't be able to boot. Use the custom Xposed by wanam (available on XDA). Or you can google for "Xposed kevintm78", this will come up with an AndroidFileHost link that you can install from Magisk. The latter is just a systemless Magisk version of Wanam's Xposed.
Here is how to get the FM radio app on R based custom roms which don't come with it preinstalled.
Note: I am pretty sure this method works on other devices which officially support FM radio, too, but I only tested on my santoni. Also note I don't take any responsibility for the changes you make to your device.
What you need:
- working rom with the FM radio app preinstalled (e.g. LineageOS, I personally used Bliss because I had a backup)
- a working root solution
- patience
In a nutshell, we are going to copy FM radio's system files from a rom where it's working and paste it into our new rom.
What to do:
- Backup (optional)
- Flash ROM with builtin FM radio
- Flash Magisk
- Find the files mentioned below
- Copy files to SD card
- Restore or Flash new rom & Magisk
- Paste files back to device
- Reboot and hope it works
Files which I found necessary for the app to work properly:
- /system/priv-app/FMRadio (whole folder, might be at /system/app or elsewhere)
- /system/etc/privapp_whitelist_com.android.fmradio.xml
- /system/lib/libfmjni.so
In theory the app folder and the library file should be enough, but it's better to take a look and copy more files than needed.
I recommend creating the original folder structure on the SD card to make pasting back easier.
I hope I could help and any feedback is appreciated.
ps. I attached the files I gathered in a zip (just copy system folder to the device root), might create a flashable one if there is interest.
do you need the app installed, andd if not can you give a link to the apk, you can use something like apk export to back it up
denesfilotas said:
Here is how to get the FM radio app on R based custom roms which don't come with it preinstalled.
Note: I am pretty sure this method works on other devices which officially support FM radio, too, but I only tested on my santoni. Also note I don't take any responsibility for the changes you make to your device.
What you need:
- working rom with the FM radio app preinstalled (e.g. LineageOS, I personally used Bliss because I had a backup)
- a working root solution
- patience
In a nutshell, we are going to copy FM radio's system files from a rom where it's working and paste it into our new rom.
What to do:
- Backup (optional)
- Flash ROM with builtin FM radio
- Flash Magisk
- Find the files mentioned below
- Copy files to SD card
- Restore or Flash new rom & Magisk
- Paste files back to device
- Reboot and hope it works
Files which I found necessary for the app to work properly:
- /system/priv-app/FMRadio (whole folder, might be at /system/app or elsewhere)
- /system/etc/privapp_whitelist_com.android.fmradio.xml
- /system/lib/libfmjni.so
In theory the app folder and the library file should be enough, but it's better to take a look and copy more files than needed.
I recommend creating the original folder structure on the SD card to make pasting back easier.
I hope I could help and any feedback is appreciated.
ps. I attached the files I gathered in a zip (just copy system folder to the device root), might create a flashable one if there is interest.
Click to expand...
Click to collapse
Pls do make a module I really need it . ( Pixel Experience + )
If you copy the mentioned files and directories that will include the apk file.
If you choose to go this route, remember that the apk you copy may be incompatible with your ROM. You can increase the likelyhood by copying the apk from a ROM that's based on the same android version.
You don't need magisk or even boot the ROM with an FM Radio app. Once it's flashed you can head over to the "Mount" section in TWRP, make sure that System is mounted and create a tape archive from the TWRP terminal or adb shell.
Code:
cd / && tar czvf /sdcard/FMRadio.tar.gz system/priv-app/FMRadio/ system/lib/libfmjni.so system/etc/privapp_whitelist_com.android.fmradio.xml
if necessary, adjust the paths to where the files actually are or cd /system instead if TWRP happens to mount your ROM in a way where everything's at /system/system because it's a system-as-root ROM. to restore the files just cd to the same directory again and tar xzvf /sdcard/FMRadio.tar.gz
if you really absolutely need a magisk module, hop over to the Magisk Developer Guide and take a few minutes to learn how to build a magisk module. if your goal is to just place some files it's very easy to do and you really just need to use a file manager, a text editor and then compress it into a zip file. as soon as you've done it once it is quite handy whenever you notice you can use it to solve another problem down the line.
if you know how to contact them and they did not already post on the matter, tell your ROM maintainer that they did not include the FMRadio app in their build. if they can fix it everyone who ever uses their build will benefit and if not, you should get an explanation for why FM Radio is broken in your ROM. if that is the case than installing the apk from somewhere else likely won't help.
SebiderSushi said:
If you copy the mentioned files and directories that will include the apk file.
You don't need magisk or even boot the ROM with an FM Radio app. Once it's flashed you can head over to the "Mount" section in TWRP and create a tape archive from the TWRP terminal or adb shell.
Code:
cd / && tar czvf /sdcard/FMRadio.tar.gz system/priv-app/FMRadio/ system/lib/libfmjni.so system/etc/privapp_whitelist_com.android.fmradio.xml
if necessary, adjust the paths to where the files actually are or cd /system instead if TWRP happens to mount your ROM in a way where everything's at /system/system because it's a system-as-root ROM. to restore the files just cd to the same directory again and tar xzvf /sdcard/FMRadio.tar.gz
if you really absolutely need a magisk module, hop over to the Magisk Developer Guide and take a few minutes to learn how to build a magisk module. if your goal is to just place some files it's very easy to do and you really just need to use a file manager, a text editor and then compress it into a zip file. as soon as you've done it once it is quite handy whenever you notice you can use it to solve another problem down the line.
if you know how to contact them, tell your ROM maintainer that they forgot to include the FMRadio app in their build. it usually is literally one line in the config for them to fix and everyone who ever uses their build will benefit that way. if not, they'll probably have a reasoning for why FM Radio is broken and installing the apk won't help you if that's the case.
Click to expand...
Click to collapse
Thanks I will try . BTW my pixel experience dosent even have any Radio app there would be no directory named radio.... So do I have to make it? Plus Google also offers its radio app which you can easily put in rom .
https://android.googlesource.com/platform/packages/apps/FMRadio
Thanks
Yes that is where the source code of the AOSP FMRadio app is hosted. If your ROM maintainer adds it to the list of packages that are supposed to be on your device it will be compiled and added to every build they create.
If you take the FMRadio apk and related files from another ROM you'd copy the whole directory so why worry about manually creating it?
SebiderSushi said:
Yes that is where the source code of the AOSP FMRadio app is hosted. If your ROM maintainer adds it to the list of packages that are supposed to be on your device it will be compiled and added to every build they create.
If you take the FMRadio apk and related files from another ROM you'd copy the whole directory so why worry about manually creating it?
Click to expand...
Click to collapse
sad thing is i was on unoffical pe+ for rosemary so i dont think he will ever add it. btw i have already installed crdroid which has fm radio so no worries thanks!
Update / correction:
I started trying out android 12 and here's what i found:
The FMRadio app included with LineageOS hasn't been ported beyond LineageOS 18.1 / android 11
The FMRadio app from AOSP hasn't beed touched for 6 years and the last branches were for android 6.
Quite some time ago there has been a 3rd party app for real FM Radio using root access if kernel and driver support exist:
App on some Google Play mirror (no longer on Google Play itself)
App of F-Droid (open source version)
The app hasnt been updated in ~7 years as well and the only developer passed away.
It (very most likely) does not work on recent android versions. At least not when i tested on LineageOS 19.1.
However, the developer kept a wiki about the topic and it appears that, at least historically, FM Radio support was an uphill battle with basically no support from google and APIs appear to be poorly or not at all standarized across device makers.
All of that information is quite old by now and i don't really know about the current situation but my takeaway is:
- FMRadio should still be supported on all Redmi 4x ROMs up to android 11 / LineageOS 18.1. you can stay on that version if you need FMRadio.
- No one brought up FMRadio support on more recent LineageOS versions and unless your custom ROM has its own FM Radio instead of using what the LineageOS codebase provides you're likely out of luck. Maybe in a couple of years / in some newer LineageOS versions the FM Radio might be brought back to life or replaced with an alternative but don't get your hopes up. This probably means that either something changed substantially with android 12 or there are simply not enough maintainers interested in FM Radio support anymore. Either way, there is no obvious way to support FM Radio when porting LineageOS 19.1 to a device that had working FM Radio prior to that.
- If your ROM is based on LineageOS 18.1 (android 11) and does not have the FM Radio app you should have a decent chance that copying the files as described in OP or installing them in a Magisk module will work. But it's still better to check back with the device maintainer because it should work on LineageOS 18.1 and a lot of custom ROMs are forks of LineageOS (e.g. crDroid) with some exceptions like OmniROM
- If your ROM is based on LineageOS 19.1 (android 12) or newer you can try copying the files but don't get your hopes up.
- It your ROM is based on LineageOS 19.1 or newer and has a working FM Radio app then congratulations, the device maintainer / the community found a way to make it work for your device or in general again.
So far that's what i know now. What a convoluted rabbit hole. I'll keep trying out things as they come but so far i believe that is the situation for FM Radio on android 12 and beyond.