LOS 19.1 Google Assistant????? - Moto G 5G Questions & Answers

Looking through the apps/hidden apps on Moto One 5g Ace after a new clean install LOS 19.1 kiev and saw 2 g00gle assistant apps, what do they do or are a part of thats required for LOS
1. com.android.hotwordenrollment.okgoogle
2. com.android.hotwordenrollment.xgoogle
the above was when viewing the installed packages with adb
why are these part of the LOS rom and are they safe to remove, pm uninstall..........
thanks

pretzells said:
Looking through the apps/hidden apps on Moto One 5g Ace after a new clean install LOS 19.1 kiev and saw 2 g00gle assistant apps, what do they do or are a part of thats required for LOS
1. com.android.hotwordenrollment.okgoogle
2. com.android.hotwordenrollment.xgoogle
the above was when viewing the installed packages with adb
why are these part of the LOS rom and are they safe to remove, pm uninstall..........
thanks
Click to expand...
Click to collapse
Can't agree generally.
Must be a device specific thing.
It's not included in the LOS19.1 I just flashed on SM-T810 even with Gapps installed.
Ask the dev and in the forum for your device.

pretzells said:
Looking through the apps/hidden apps on Moto One 5g Ace after a new clean install LOS 19.1 kiev and saw 2 g00gle assistant apps, what do they do or are a part of thats required for LOS
1. com.android.hotwordenrollment.okgoogle
2. com.android.hotwordenrollment.xgoogle
the above was when viewing the installed packages with adb
why are these part of the LOS rom and are they safe to remove, pm uninstall..........
thanks
Click to expand...
Click to collapse
It is safe to remove them. I have done so without repercussions. By the way, this is my most hated Google app.

I disabled them through abd but want to remove them, I have not installed gapps, not interested, why is this part of the LOS rom?? I will then uninstall them completely, thanks for the replies, have to admit i was surprised to see them in the installed software list. Thanks!
Also, cacerts google is also on my phone?? Evidently its this
"The cacerts file is a collection of trusted certificate authority (CA) certificates. Sun Microsystems™ includes a cacerts file with its SSL support in the Java™ Secure Socket Extension (JSSE) tool kit and JDK 1.4. x. It contains certificate references for well-known Certificate authorities, such as VeriSign™"

bmwdroid said:
Can't agree generally.
Must be a device specific thing.
It's not included in the LOS19.1 I just flashed on SM-T810 even with Gapps installed.
Ask the dev and in the forum for your device.
Click to expand...
Click to collapse
yah, I posted in the LOS section but this thread was moved here, I guess because I stated the phone I used. could be a unique event but RETIEF above had the same issue as well

Related

ROM COPPERHEAD OS - info

No one have tried the new ROM Copperhead OS ?
Can i try to install it as secondary rom in MultiRom ?
I'm on Cyanogen CAF 12.1 now...
thank you all
chickygamon said:
No one have tried the new ROM Copperhead OS ?
Can i try to install it as secondary rom in MultiRom ?
I'm on Cyanogen CAF 12.1 now...
thank you all
Click to expand...
Click to collapse
Hi! I've installed it in multirom with a stock 5.0.1 as primary and it works, just tried it for few minutes.
just be sure to have the latest bootolader (HHZ12h) or installation will fail.
Flashing a bootloader
Hi,
I have a Nexus 5 and I use Multirom with it. My default ROM is Lollipop 5.1.1 and a secondary ROM, which I mostly use, is Marshmallow 6.0 (xTraSmooth). I want to install CopperheadOS, but it says when installing, that I must have HHZ12h bootloader in order to install (as stated in a previous post). My current bootloader is HHZ11k. If I install HHZ12h bootloader by flashing a zip file which includes LMY48B_Radio+Bootloader-HHZ12h will it cause anything that prevents Lollipop or Marshmallow to work properly?
ithippi said:
Hi,
I have a Nexus 5 and I use Multirom with it. My default ROM is Lollipop 5.1.1 and a secondary ROM, which I mostly use, is Marshmallow 6.0 (xTraSmooth). I want to install CopperheadOS, but it says when installing, that I must have HHZ12h bootloader in order to install (as stated in a previous post). My current bootloader is HHZ11k. If I install HHZ12h bootloader by flashing a zip file which includes LMY48B_Radio+Bootloader-HHZ12h will it cause anything that prevents Lollipop or Marshmallow to work properly?
Click to expand...
Click to collapse
You don't need to downgrade the bootloader, just modify the updater script of the rom ( deleting the string containing the bootloader version or replacing with your current version), then it will install just fine.
Can anybody provide link on COPPERHEAD OS ? CHEERS!
Pretoriano80 said:
You don't need to downgrade the bootloader, just modify the updater script of the rom ( deleting the string containing the bootloader version or replacing with your current version), then it will install just fine.
Click to expand...
Click to collapse
Thanks! I haven't tried that yet, but I will. First I thought I can just replace HHZ12h with HHZ11k using text editor, but then I noticed there are guides which suggest that it isn't quite that easy. I might be wrong about that, will see when I have enough time to read up on the subject.
Sent from my Nexus 5 using XDA Free mobile app
ithippi said:
Thanks! I haven't tried that yet, but I will. First I thought I can just replace HHZ12h with HHZ11k using text editor, but then I noticed there are guides which suggest that it isn't quite that easy. I might be wrong about that, will see when I have enough time to read up on the subject.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It's easy, just extract the rom, go to Meta-Inf/com/google/android and modify the "updater-script". That's all, rebuild the zip and flash in recovery.
Edit: you can do it without using a PC, by using a file manager on your device.
Ross Korolov said:
Can anybody provide link on COPPERHEAD OS ? CHEERS!
Click to expand...
Click to collapse
here it is
https://copperhead.co/android/
....
Is this rom any good?
bonedriven said:
Is this rom any good?
Click to expand...
Click to collapse
Just installed it on a Nexus 5x and it works flawless. It has most of the standard stuff but is different from the rest in that it is supposed to be security oriented. That means no default root (but rooting should be possible).
I didn't try to add Google stuff yet and probably won't even try to add that spyware but it does have the F-Droid app store.
There are some extra options to secure the memory if required, and the documentation is (so far) very good (for example the install guide and the technical overview).
Currently running it on my Nexus 5x and N5. works great. Anything you are missing you can find on F-Droid. I find the lack of data usage to be delightful; when facebook or ebaum videos auto load on other software, they are stopped on copperhead. very happy with the security.
The only thing i can not make work is voice to text, and I have a ticket in with copperhead. who cares, I have fast thumbs.
Nexus + Copperhead = Happy Gopher!
mg.degroot said:
Just installed it on a Nexus 5x and it works flawless. It has most of the standard stuff but is different from the rest in that it is supposed to be security oriented. That means no default root (but rooting should be possible).
I didn't try to add Google stuff yet and probably won't even try to add that spyware but it does have the F-Droid app store.
There are some extra options to secure the memory if required, and the documentation is (so far) very good (for example the install guide and the technical overview).
Click to expand...
Click to collapse
happy_gopher said:
Currently running it on my Nexus 5x and N5. works great. Anything you are missing you can find on F-Droid. I find the lack of data usage to be delightful; when facebook or ebaum videos auto load on other software, they are stopped on copperhead. very happy with the security.
The only thing i can not make work is voice to text, and I have a ticket in with copperhead. who cares, I have fast thumbs.
Nexus + Copperhead = Happy Gopher!
Click to expand...
Click to collapse
Thanks for the feedback. I guess manual apk installation is also possible?
I'm thinking about picking up a Nexus 5 as a backup device, and CopperheadOS seems like something fun to play with, instead of just installing CM13. Can I install TWRP as recovery on devices like the Nexus 5 that don't check for locked bootloaders? Can I run it as basically another ROM –*unlocked developer options, root, TWRP, etc.? I realize the OS exists for enhanced security, but I'd like to make a few tradeoffs.
Unfortunately, you can not run TWRP with copperhead, it wants full control of the phone for security reasons. Its not meant to be a developer OS with access to all the bits, so you kind of need to want a OS in a box that you can deal with.
But I have to say, despite its shortcomings of not having google services, it works pretty much flawless on my 5 and 5x. i miss google maps app, but it works 100% via chromium browser as a favorite, and I have only found 2 apps I can not import via apkmirror, one being Waze, the other is my local public transportation app. other than that, i feel like I'm safe from prying eyes.
Hg
happy_gopher said:
Unfortunately, you can not run TWRP with copperhead, it wants full control of the phone for security reasons. Its not meant to be a developer OS with access to all the bits, so you kind of need to want a OS in a box that you can deal with.
But I have to say, despite its shortcomings of not having google services, it works pretty much flawless on my 5 and 5x. i miss google maps app, but it works 100% via chromium browser as a favorite, and I have only found 2 apps I can not import via apkmirror, one being Waze, the other is my local public transportation app. other than that, i feel like I'm safe from prying eyes.
Hg
Click to expand...
Click to collapse
Thanks for your response. I'm a fan of CyanogenMod, and I'm not unhappy their security or features, but I wanted to play around with CopperheadOS. I understand the tradeoff between security and convenience, but I'm not willing to sacrifice TWRP in the mix. Oh, well – if I ever have need of an OS solely for its security track record, I know where to go.
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
NewDayRising said:
Thanks for your response. I'm a fan of CyanogenMod, and I'm not unhappy their security or features, but I wanted to play around with CopperheadOS. I understand the tradeoff between security and convenience, but I'm not willing to sacrifice TWRP in the mix. Oh, well – if I ever have need of an OS solely for its security track record, I know where to go.
Click to expand...
Click to collapse
Switch debugging OFF and don't lock bootloader after CopperheadOS install and u will be able to boot TWRP via
fastboot boot recovery.img [TWRP]
I'm currently experimenting with root privileges on CopperheadOS on Nexus 5X. Still haven’t tried xposed framework.
Security features r quite good, especially different lock code && encryption password and memory protection, but, there is a lack of fine privacy control (Privacy Guard) as in CyanogenMod and firewall, hence the need for root.
CopperheadOS on Nexus5
dnaod said:
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
Click to expand...
Click to collapse
I've been using CopperheadOS for a few weeks now on the Nexus5. Received the latests OTA a few days ago and applied without issue.
Installed it via TWRP. Have rooted the device with SuperSU, though have to re-root after re-flashing recovery after each OTA.
It's been working great.
Unfortunately I don't have the img any more
The one I flashed was https://builds.copperhead.co/builds/hammerhead-factory-2016.08.09.06.24.33.tar.xz
download link
dnaod said:
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
Click to expand...
Click to collapse
https:// builds.copperhead.co /builds/hammerhead-factory-2016.09.07.19.27.04.tar.xz
Remove spaces. I'm a new member and can't post links.

[TOOL] Xiaomi ADB/Fastboot Tools

Hi everyone!
I'm Saki, a long time tech enthusiast, Xiaomi fan and developer. More than a year ago I started working on a program, called Xiaomi ADB/Fastboot Tools, that makes it easy to manipulate Xiaomi phones using ADB and Fastboot, which are official debugging tools for Android. They have command line interfaces and they can be used for a variety of things, including but not limited to uninstalling system applications, overriding screen density (DPI), enabling camera2 and flashing ROMs. This application makes their most popular features easily accessible to less tech-savvy users by providing a GUI to interact with.
Modules
App Manager - Uninstall/reinstall/disable/enable system apps and services on demand
Camera2 - Enable Camera2 and EIS (TWRP required)
File Explorer - Transfer files between a device and a computer using ADB
Screen density - Tweak screen density by overriding the DPI value
Screen resolution - Tweak screen resolution by overriding the width and height values
Device properties - Retrieve tons of statistics and information about your device
Flasher - Flash any partition with an image, boot to any image or flash a Fastboot ROM (unlocked bootloader required)
Wiper - Wipe the cache or perform a factory reset
OEM Unlocker & Locker - Lock or unlock the bootloader (unlocking is only supported by Android One devices)
ROM Downloader - Get links to the latest MIUI Fastboot ROMs or download them right away
Rebooter - Advanced rebooting options using ADB/Fastboot
The application has been in the works for over a year, some older versions even got posted on Reddit where the reception was overwhelmingly positive. The project is free and open-source, the source code is publicly available on GitHub so anyone can inspect the code or fork the project for themselves and add their own modifications to it if they want.
The Xiaomi/ADB Fastboot Tools was originally written in C# for Windows but I received a lot of requests to make it work on Mac and Linux so I rewrote the whole thing for the JVM, so it runs on Windows, MacOS and Linux as of today.
For more information, including instructions, screenshot, frequently asked questions and download, visit the project page on GitHub.
If you experience any issues, read the FAQ. If you cannot find the solution there, leave a comment here or open an issue case on GitHub. Feedback is highly appreciated!
For additional help with Xiaomi devices, feel free to visit the Xiaomi Community on Discord.
Thanks for reading and enjoy :angel:
Tell me. More about the EIS... Does it work with app like open camera...
Because EIS in Poco doesn't work in any camera app except stock camera
Sent from my POCOPHONE F1 using Tapatalk
Mr.Sm1th said:
Tell me. More about the EIS... Does it work with app like open camera...
Because EIS in Poco doesn't work in any camera app except stock camera
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Not sure if there's anything different about the Poco, but the method used here is equivalent to enabling persist.camera.eis.enable. If you tried enabling that and you didn't get anything out of it, this won't make any difference. The options to enable Camera2 and EIS are mainly for Gcam.
With this tools it's more easy to remove the bloatware as with a regular minimal adb?
Mikael1013 said:
With this tools it's more easy to remove the bloatware as with a regular minimal adb?
Click to expand...
Click to collapse
To me, checking a few boxes and clicking a button is much easier than entering a line of arguments for each application.
hi, i can't open it on my pc. i'm using windows 10 with java se development kit 11 and java runtime environment 8 installed.
Nice to see Xiaomi Reddit moderator here posting about the tool. For anyone asking: it works well for every MIUI version I tried. Though I've moved back to older version may be v2.0.0.2 cause that doesn't require java to run and I don't feel comfortable to install java bloatware just to use this tool.
Thank you Saki for the tool.
could you post link for that older version that doesn't require java
chilling said:
hi, i can't open it on my pc. i'm using windows 10 with java se development kit 11 and java runtime environment 8 installed.
Click to expand...
Click to collapse
If you have the Java 11 SDK, you have the JRE 11 as well. I'm afraid you have to download and use JavaFX with that JRE or uninstall Java 11 to be able to use JRE 8.
DomagojX said:
could you post link for that older version that doesn't require java
Click to expand...
Click to collapse
It's in the original post. Be aware that it doesn't have nearly as many features and can also contain a few bugs I haven't come across.
Is there a way to restore the Mi Cleaner app without doing a factory reset? (Redmi 4X running MIUI 10.3)
Nathan-NL said:
Is there a way to restore the Mi Cleaner app without doing a factory reset? (Redmi 4X running MIUI 10.3)
Click to expand...
Click to collapse
None that I know of.
Saki_EU said:
If you have the Java 11 SDK, you have the JRE 11 as well. I'm afraid you have to download and use JavaFX with that JRE or uninstall Java 11 to be able to use JRE 8.
Click to expand...
Click to collapse
already uninstalled jre 8. version 5.3 now works. thank you!
chilling said:
already uninstalled jre 8. version 5.3 now works. thank you!
Click to expand...
Click to collapse
Great to hear! So sorry you had to wait so long for the Java 11 compatible release, Oracle messed things up bad!
Version 5.4 is out!
Changelog and download on GitHub.
Thank you for app.
Nice app! Can it uninstall system apps too?
Version 6.0 is out!
Changelog:
- New module in ADB: File Explorer
- Added a check for updates on startup
- Minor UI changes
- Updated Kotlin library
- Minor code optimisations
Download link in the OP.
bowlofsausage said:
Nice app! Can it uninstall system apps too?
Click to expand...
Click to collapse
That's what it's for! It doesn't even offer apps for uninstallation that you can easily uninstall by yourself
Saki_EU said:
That's what it's for! It doesn't even offer apps for uninstallation that you can easily uninstall by yourself
Click to expand...
Click to collapse
I see line to add packages to uninstall list by name and i suppose i can unninastal it then. Can I see all list of apps at once not by adding by myself? Now on application start i only see some miui and google apps to uninstall, no other packages names

unable to process request due to missing initial state

I followed the instructions here to put LOS 18.1 on the Uniherz Jelly 2:
[ROM] [UNOFFICIAL] Lineage OS 17.1 | Unihertz Jelly 2
https://drive.google.com/drive/u/0/folders/1VSmj_-a1PYNzFWtUfbsDGWg4uIh-Tgkd This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW...
forum.xda-developers.com
Next used the infos in this thread to make it spoof and put MicroG ( 0.2.14.204215 ) on it:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com
So now the main thing I wanted out of the latter is working - a car sharing app works on the phone.
I attempted however to run another mobility app, which does electric scooters and while it didn't complain about Play Services anymore, it eventually opened up some kind of empty browser window with the following text in it:
Unable to process request due to missing initial state. This may happen if browser sessionStoraage is inaccessible or accidentally cleared.
Click to expand...
Click to collapse
"Cloud Mesaging" in MicroG is not switched on, but doubt it is that. I added no Location modules (backends) as the GPS seems to work so well. Everything is ticked under the MicroG requirements, but I tried to switch on permission to access location in the background on MicroG but it will not let me switch it on. I'm scared to update MicroG from F-Droid to a newer version, since I followed instructions from somewhere to install it from Magisk along with something else which patched the services.jar to spoof.
Any ideas as to how to fix this problem and what things to try, in what order?

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.

[ROM][UNOFFICIAL][A13.0][sunfish Pixel4a 4G] crDroid v9.5+ with GApps

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device, while adding a lot of eye-candy (ie features).
Features:
https://github.com/crdroidandroid
Screenshots
https://crdroid.net/#gallery
Flashing Instructions:
See the post: https://forum.xda-developers.com/t/...crdroid-v9-5-with-gapps.4593649/post-88663897
Pre-installation:
Download the ROM
download the May 2023 stock firmware (*NEW STEP*)
Backup any important data
Have an exit strategy if it goes wrong
GApps are included
Magisk 25.0 or newer for root (after first boot) - NOTE: v26.1 is the currently latest stable build.
NB: The FASTBOOT release method i use is not that well documented. But, iuts basuically what occurs from flashing google supplied firmware releases, so it must be at least half good. It's a few more build steps & time, but it also makes it far easier for me to flash ( and for you). Not having a working TWRP, I dont understand (apart from the extra steps. time & storage) why all ROMs for P4A are not released like this.
Update installation:
Leave out the -w from the command. Its hard to miss
Sources:
ROM: https://github.com/crdroidandroid
Device: https://github.com/LineageOS/android_device_google_sunfish
Kernel: https://github.com/crdroidandroid/android_kernel_google_msm-4.14
Vendor: https://github.com/TheMuppets/proprietary_vendor_google_sunfish
Gapps: https://github.com/BlissRoms/platform_vendor_bliss
Download:
ROM crDroidAndroid-13.0-20230619-sunfish-v9.5-UNOFFICIAL-DiamondJohn-FASTBOOT.zip MD5: 575B8DEDB8371839AD38888BBB4F820E
BOOT IMAGE crDroidAndroid-13.0-20230619-sunfish-v9.5-UNOFFICIAL-DiamondJohn-FASTBOOT-boot.img MD5: A9BD232C4773E4B6C5A5BA19E2C1DC68
Changelog: see attached in the release post listed above as flashing instructions
Known issues:
You tell the rest of us!
Visit official website @ crDroid.net https://crdroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help the crDroid team pay server costs
OR
Donate to help others
The initial "out of the box" builds of crDroid 9.5 (A13) kept failing at the veeeeery last stage, where it would try to build a flashable image, and would fail the check that it would fit on the devices partitions.
I then built a non-googled version (by accident) and that succeeded. Obviously because the google apps installed by default, by crDroid, were taking too much space.
I spent HOURS trying to find where in crDroid the list of which google apps are installed, but failed. I am sure if someone pointed it out to me, I would slap my forehead, and say "obviously"!. And that is one of the difficulties in building crDroid. Other ROMs have telegram channels where one can speak directly with the ROM devs to ask questions. All I could find for crDroid was a user channel.
So, to get a build with google installed, I set it up to build crDroid without google, and added in the code from Bliss (a ROM I have already built, and they have addressed the size issue specifically for pixel devices. inc sunfish) to add google services & apps. That worked! I also noticed that there is an official release here for another device, on XDA, that also has no google...
The google apps installed by what I have done are actually pretty comprehensive. Below is a list:
GoogleExtShared
GooglePrintRecommendationService
DocumentsUIGoogle
GooglePackageInstaller
TagGoogle
CalculatorGooglePrebuilt
CalendarGooglePrebuilt
Chrome-Stub
DevicePolicyPrebuilt
GoogleContacts
GoogleTTS
LatinIMEGooglePrebuilt
LocationHistoryPrebuilt
Maps
MarkupGoogle
ModuleMetadataGoogle
Photos
PixelThemesStub
PixelThemesStub2022_and_newer
PrebuiltDeskClockGoogle
PrebuiltGmail
SoundPickerPrebuilt
TrichromeLibrary-Stub
WebViewGoogle-Stub
talkback
AdaptiveVPNPrebuilt
AndroidAutoStubPrebuilt
ConfigUpdater
DeviceIntelligenceNetworkPrebuilt
DevicePersonalizationPrebuiltPixel2022
FilesPrebuilt
GoogleDialer
GoogleOneTimeInitializer
GoogleRestorePrebuilt
PartnerSetupPrebuilt
Phonesky
PrebuiltBugle
PrebuiltGmsCore
PrebuiltGmsCoreSc_AdsDynamite
PrebuiltGmsCoreSc_CronetDynamite
PrebuiltGmsCoreSc_DynamiteLoader
PrebuiltGmsCoreSc_DynamiteModulesA
PrebuiltGmsCoreSc_DynamiteModulesC
PrebuiltGmsCoreSc_GoogleCertificates
PrebuiltGmsCoreSc_MapsDynamite
PrebuiltGmsCoreSc_MeasurementDynamite
AndroidPlatformServices
SafetyHubPrebuilt
ScribePrebuilt
SecurityHubPrebuilt
SettingsIntelligenceGooglePrebuilt
SetupWizardPrebuilt
TurboPrebuilt
Velvet
WellbeingPrebuilt
EmergencyInfoGoogleNoUi
Flipendo
GoogleServicesFramework
PixelSetupWizard
QuickAccessWallet
StorageManagerGoogle
TurboAdapter
WallpaperPickerGoogleRelease
com.google.android.dialer.support
Personally, im a little chuffed I got it working. I would also like to say, the instrctions for building crDroid on trheir guthuib page are really lacking. I had to use what I learnt from other ROMs (and their instructions) to even get started.
AFTER I built the above, I founmd that someone else has actually built crDroid with googl;e installed, and posted it up on Android File Host. I havent tested their build, but it was 10 days ago now, and there have been extra commits since that build. Specifically the brightness slider styles.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
I think a few years ago I came across this guys AFH uploads when I had a Nexus 5, and I could not find anyway to contact him back then.
MY future plans for this ROM.
Firstly, this is UNOFFICIAL. I am not associated with crDroid in anyway. Any of you could do the same as what I have done.
If there is a bug, 1 of three things could happen.
1. Its something you have added to the ROM. Its now up to you to fix.
2. If the bug is sunfish specific, but I dont get bothered by the same bug, Meh. Chances are I wont fix it
3. Its a crDroid or LOS bug, I will direct you to post the bug with crDroid / LOS.
By all means, post the bug here to let others & me know and maybe help you, but do not get perturbed If I dont start spending time coding to fix it.
Changes to the ROM I foresee right now, since it is a personal share of the ROM I plan to run on my daily, primarily for ME, are:
The QS tile headers are a Japanese anime theme. I will probably replace those with some abstract textures
The default wallpaper which appears on the lockscreen before you unlock, although is better than others, I will change to another space theme to match my Live Wallpaper
The theming colours are missing Teal!?!? I will probably replace an existing colour.
Im thinking *maybe* the boot animation to the old nexus prime prime one (see below)
maybe others I haven't noticed thus far, but I dont think anything too crazy or offensive.
NO GUARANNTEE, but since crDroid add features very often (eg brightness slider styles since the official v9.5 release), I will probably go with close to monthly builds to keep up.
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
chozendroid said:
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
Click to expand...
Click to collapse
Most of your questions are answered explicitly by my post above yours.
As for minimal GApps, I also generally previously flashed min GApps, so as to exclude anything I can get from the playstore. I actually read the list of included GApps after I had started the build (over 150,000 steps) and thought about cutting it back, and restarting. However, It is simple to Force_Close-Clear-Freeze-Hide any app that you dont want, which practically makes it as if it was never installed. If your rooted, yu can use my app TeMeFI to do it. Thats how I do it, including i5tens such as MatLab & Eleven ( as I use Vinyl from the playstore) and Viper instead of MusicFX. Everyone has their own preferences,
I am NOT going to build & release multiple version with different levels of GApps.
DiamondJohn said:
Most of your questions are answered explicitly by my post above yours.
As for minimal GApps, I also generally previously flashed min GApps, so as to exclude anything I can get from the playstore. I actually read the list of included GApps after I had started the build (over 150,000 steps) and thought about cutting it back, and restarting. However, It is simple to Force_Close-Clear-Freeze-Hide any app that you dont want, which practically makes it as if it was never installed. If your rooted, yu can use my app TeMeFI to do it. Thats how I do it, including i5tens such as MatLab & Eleven ( as I use Vinyl from the playstore) and Viper instead of MusicFX. Everyone has their own preferences,
I am NOT going to build & release multiple version with different levels of GApps.
Click to expand...
Click to collapse
I appreciate the response. It is your build, so I fully respect your decisions. I personally don't root (Google Pay issues and intermittent errors with specific banking apps), so I'll just have to stick with the basic approach of hiding whatever apps I don't use. Definitely look forward to giving it a try over the weekend when I have some downtime.
chozendroid said:
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Click to expand...
Click to collapse
And to state the obvious, I LOVE this device and build custom ROMs for it, for me to use.
A few weeks ago I watched a number of videos about how this device is still a good choice today. So we two are not the only ones.
https://www.youtube.com/results?search_query=pixel+4a+2023
chozendroid said:
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
Click to expand...
Click to collapse
Actually, on the other OFFICAL release of crDroid for another device, he called his de-googled build "VANILLA". Were you asking about a ROM with any google whatsoever? I tried adding Google services via a Magsk module and it wasnt great. The keyboard never popped up when I entered a text field, and I couldnt install the updated GBoard. I had to install the M$ keyboard. AND that GApps module obviously requires root/Magisk.
I personally would of assumed "VANILLA" android (ie ASOP / Pixel Device) includes Google Services, but meh, what do I know.
chozendroid said:
I appreciate the response. It is your build, so I fully respect your decisions. I personally don't root (Google Pay issues and intermittent errors with specific banking apps), so I'll just have to stick with the basic approach of hiding whatever apps I don't use. Definitely look forward to giving it a try over the weekend when I have some downtime.
Click to expand...
Click to collapse
As for Force_Close-Clear-Freeze-Hide, im pretty sure you don't have to root the device.
And maybe, dont forget the link I posted to the other android file host build. Maybe he has built with less google stuff. But, I think he built before the brightness slider themes were added and who knows when the next build will occur. He has no contact details. I would like to know how he got GApps to be included.
I dont know anything about development (but been using custom roms since the nexus 4 days), but in my mi 9 se. I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload). As i am new with this P4A i wish to know why a similar aproach doesn't work with our device.
DiamondJohn said:
Actually, on the other OFFICAL release of crDroid for another device, he called his de-googled build "VANILLA". Were you asking about a ROM with any google whatsoever?
Click to expand...
Click to collapse
This is exactly what I was asking about actually. A de-googled/vanilla build which would allow me to just sideload minimal Gapps via adb
prog19 said:
I dont know anything about development (but been using custom roms since the nexus 4 days), but in my mi 9 se. I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload). As i am new with this P4A i wish to know why a similar aproach doesn't work with our device.
Click to expand...
Click to collapse
Using ADB sideload, you HAVE to be on a specific version of a ROM; especially for the first flash or when switching between ROMs. This fastboot method first flashes any prerequisites, reboots, then completes the flash. All in a single step, no confusion in getting the correct starting point. To me its a LOT better, but more work for the DEV (ie ME). If you have flashed Bliss, then you would know you actually have to first flash an older fastboot file, and then install the latest version via sideload.
My method is a single step EVERY time I do a release. Including for those people who install for the first time, regardless of what ROM/firmware they are coming from. The only difference will be the -w parameter for the first time. They onlyt have to insure they are running a valid platform-tools (ie ADB/fastboot)
So, the ROM sideload way works for P4A, but this way is easier to install. In building, I first get the sideload file, but then have to run a few more steps and build time to get the sideload file out, and then a few more steps. ie its more work for me. But I think better for flashing; including for me. When I first flash the official Bliss, I made a mistake and the ROM was not working correctly
prog19 said:
.... I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload)....
Click to expand...
Click to collapse
Im not 100% certain, but I do not think you can add/overlay GApps by sideloading a GApps file over a P4A ROM. Like on older devices using TWRP. Or am I wrong? If Im wrong, then I will build without GApps and people can choose their GApps level/coverage. Easier for me, and better for others.
chozendroid said:
This is exactly what I was asking about actually. A de-googled/vanilla build which would allow me to just sideload minimal Gapps via adb
Click to expand...
Click to collapse
Again, are you 100% certain you can sideload GApps onto an existing ROM on the Pixel 4A? read above. If you can, then that's what I will build from now on. Much easier for me.
DiamondJohn said:
Again, are you 100% certain you can sideload GApps onto an existing ROM on the Pixel 4A? read above. If you can, then that's what I will build from now on. Much easier for me.
Click to expand...
Click to collapse
I'm not sure because I haven't seen any P4A ROMs based on Android 13 without built-in Gapps thus far. But like @prog19 mentioned, this is how it works for other devices. That's what I do with my OP6T, but I know each device has it's nuances, hence the reason I asked. It's not a necessity. I just find that it creates a lighter initial installation which is a matter of personal preference.
DiamondJohn said:
DOPO aver creato quanto sopra, ho scoperto che qualcun altro ha effettivamente creato crDroid con googl;e installato e l'ha pubblicato su Android File Host. Non ho testato la loro build, ma sono passati 10 giorni e ci sono stati commit extra da quella build. In particolare gli stili del dispositivo di scorrimento della luminosità.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
Penso che qualche anno fa mi sono imbattuto in questi caricamenti AFH di questo ragazzo quando avevo un Nexus 5, e non sono riuscito a trovarlo comunque per contattarlo allora.
Click to expand...
Click to collapse
DiamondJohn said:
AFTER I built the above, I founmd that someone else has actually built crDroid with googl;e installed, and posted it up on Android File Host. I havent tested their build, but it was 10 days ago now, and there have been extra commits since that build. Specifically the brightness slider styles.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
I think a few years ago I came across this guys AFH uploads when I had a Nexus 5, and I could not find anyway to contact him back then.
Click to expand...
Click to collapse
Hi! I have installed this github Rom, but have few little bugs, your rom is different? I want try it
DiamondJohn said:
Using ADB sideload, you HAVE to be on a specific version of a ROM; especially for the first flash or when switching between ROMs. This fastboot method first flashes any prerequisites, reboots, then completes the flash. All in a single step, no confusion in getting the correct starting point. To me its a LOT better, but more work for the DEV (ie ME). If you have flashed Bliss, then you would know you actually have to first flash an older fastboot file, and then install the latest version via sideload.
My method is a single step EVERY time I do a release. Including for those people who install for the first time, regardless of what ROM/firmware they are coming from. The only difference will be the -w parameter for the first time. They onlyt have to insure they are running a valid platform-tools (ie ADB/fastboot)
So, the ROM sideload way works for P4A, but this way is easier to install. In building, I first get the sideload file, but then have to run a few more steps and build time to get the sideload file out, and then a few more steps. ie its more work for me. But I think better for flashing; including for me. When I first flash the official Bliss, I made a mistake and the ROM was not working correctly
Im not 100% certain, but I do not think you can add/overlay GApps by sideloading a GApps file over a P4A ROM. Like on older devices using TWRP. Or am I wrong? If Im wrong, then I will build without GApps and people can choose their GApps level/coverage. Easier for me, and better for others.
Click to expand...
Click to collapse
Thank you for the very detailed answer
Marcia8246 said:
Hi! I have installed this github Rom, but have few little bugs, your rom is different? I want try it
Click to expand...
Click to collapse
Yes. I already explained the difference, in addition to not knowing any details that I have also doc'd in the OP.
To be clear, I know nothing more about this ROM than you. Actually, even less, as you have flashed it.
chozendroid said:
I'm not sure because I haven't seen any P4A ROMs based on Android 13 without built-in Gapps thus far. But like @prog19 mentioned, this is how it works for other devices. That's what I do with my OP6T, but I know each device has it's nuances, hence the reason I asked. It's not a necessity. I just find that it creates a lighter initial installation which is a matter of personal preference.
Click to expand...
Click to collapse
As for working for "other devices", thats one of the changes in Googles newer devices. But the same would go for the Pixel 4A 5G, the 5, 6 & 7 series pixel devices. Try and find a single sideloadable ZIP that makes an incremental change on one of these devices, to one of the system partitions. And its not just google. Thats one of the reasons to use Magisk modules, they allow a partial targeted change to a RO partitions.
I think there is an official A13 GrapheneOS ROM for the Pixel 4A, that has no GApps.
FYI: Im kicking off a kinda test build, with a smaller google footprint, and 11 modified header QS images.
Also ONLY on my installed ROM on personal device (NOT in the ROM). I have debloated Aperture (the Camera)l, Eleven & Audio FX and installed Google Camera (It has "Night Vision" which I dont know if its better, but I like the option), Vinyl as my music player, and ViperFX as my Eq. Viper eq's the sound for the player, but not from some other apps.
See below post for how:
[OFFICIAL] BlissRom 16 [Typhoon] [sunfish][Android 13]
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience. Our focus...
forum.xda-developers.com
The RisingOS actually has a good Music player, that is updated on F-Droid, I would probably go with that, if I remembered the name, and wasn't committed with boot scripts to Vinyl. Since its part of a ROM, probably get more attention.
I also liked the calculator on RisingOS. I'll check if someone can get me the APK and it works, and the name of the Music player.
FYI: I did a test build over last night, but three of my changes didn't go as expected, so I will need to fix them and do another build before release. DOH!
The boot animation frame rate is WAAAaay to fast
One of my new QS Tile headers isnt displaying. Dont get it as it is literally the same as another one just a different shade/colour pallet
The default wallpaper remained unchanged.
I did note that there was a small flurry of changes (bug fixes, not new features)
One of the new headers is interesting, but I dont think I will personally use it (ironically I would use the one that failed...)
Its basically a view of the circuit board from the back. Kind-a simulates you are actually dragging the screen off to reveal the circuits underneath. If only I could find a photo of the correct side of the main board and not from the back. Anyone?
Another FYI, I installed ReVAnced as root and it went without a hitch, All I did was:
Downloaded & installed the revanced manager APK
Started it up to see which version of You Tube it expected
Source the correct version of youtube from APK Mirror OR APK pure etc etc etc
Installed the base correct & expected Youtube
Ran ReVanced Manager. Selected it to apply the "Default Patching" BUT turned off the MicroG support
Ran the patching
Installed it as root
rebooted
Detach youtube from playstore
Enjoy!
forgot step 8.5 for ReVanced install, Detached it from the playstore
also realised the reason / where I failed on the three points of the ROM build issues.

Categories

Resources