yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
Thank you for releasing RisingOS for our Pixel 4a.

I'm recently starting to try RisingOS v1.1 for my spare phone.

I tried RisingOS for the first time on my Pixel 6a and liked it because it was a very well put together ROM. When I was hoping to try RisingOS on my spare Pixel 4a, luckily I found it was released and started testing.

I don't have a spare SIM for testing, so I haven't been able to check the mobile communication system, but other than that, I've had almost no problems in normal use. So far, I have only noticed the following points.

(1) Battery consumption(?) of com.android.hbmsvmanager

"High Brightness Mode Manager", which seems to be a thing, was displayed at the top of the battery uage list.

It does not seem to waste battery power extremely, but I was concerned about it, so I changed it to "Restircted" in "App battery usage". The app no longer appears in the battery status list.

Actually, this problem also existed in crDroid 9.5 20230606build. when I tried crDroid, changing to "Restricted" did not (it seemed) enough to deal with it, so I uninstalled it with "adb shell pm uninstall -k --user 0 com.android.hbmsvmanager".

PS. I'm sorry, I forgot to log when I had the problem.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Check your PM's
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
NEW BUILD!

See OP for download.

The change log is borked in RisingOS, so I fixed it AFTER I built the ROM (and saw it was still broken) Attached is the log since around my last release.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
FYI Until recently (about the last 5 days), this ROM had more downloads than crDroid!! which I am keeping alive for at least ME!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
Thank you for 20230617 build release.

I tested it, but I didn't get good result.

The problems identified are as follows.

(1) com.android.hbmsvmanager battery drain

(2) cannot unlink Ring volume & Notification volume

(3) NFC cannot enable

(1) is a problem that has existed previous build and can be handled by the user, (2) and (3) did not exist in previous.

Clean Install (no restoration)

Dirty Install (update over 20230602)

I got same result both case.

After the problem (3) In order to restore NFC,

I had to go through the initial setup once using Google Stock ROM. (only flashing the Stock ROM did not restore NFC)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
As I am not "developing" this ROM, just providing UNOFFICIAL builds; so there is somd messaging massaging to use a LOS device tree. Therefore, I wont be fixing any. Your best bet is to check on githib issues, or maybe politely checking with someone running an Official build. However, if they are running official, they would be running an older build; my builds are closer to Nightly's. But I think you said the issues were in the first also, and therefore by timing, closer to official. But, its most likely be a LineageOS device tree issue.

(3) is a pretty major issue in my eyes (not that I use it OR this ROM), so maybe others should confirm. Thing to remember, its all a work in progress for RisingOS & LineageOS

I wouldn't expect too much chance of a difference, as its a RO device, so it blows away/overwrites the whole & every system partition. But it is possible a dirty flash will bring along bad data partition settings &/or flags.

HUH? so NFC didnt work on the latest stock ROM? there is a new July Firmware.

Is it working now? I don't understand?

I just checked my latest crDroid build, which uses the same device tree, and I can turn NFC on/off using the quick tiles (I have no idea where to find it in settings as the search is broken). I tested my security FOB to enter my apartment's block, and it read it.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
Thanks your reply.

Since you have provided us with a new build, I feel it is necessary to let you know that I have used it and that is what the situation was. This is why I am posting with that intention.

After NFC was disabled, it was not possible to just flash the StockROM.

NFC could not be restored until the initial setup was completed with that StockROM.

I even ran the re-setup with 202305 StockROM to get NFC back enabled again.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
@klazyStrida One thing I remember now when I tested NFC on my crDroid phone, I turned on NFC with the quick tile, but when I started the NFC tag reader APP, it said NFC was off and took me to the NFC settings, where it was off. So I turned it ON there as well, and thats when the app read my tag. So, maybe try the same in this rom; ie two locations to switch it on/off. The app I used was "TagInfo" by NXP, from the playstore. I think a few years ago, I used to freak my friends out, as it loudly beeped when I held their Credit Card near my phone, and I then thanked them for the $100.😛

Just purely a suggestion, when posting bugs for info only (AND that is a GOOD thing for users of this ROM, and as such I highly encourage it), maybe precede the list with an FYI. It also gives me something to explicitly test in crDroid.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
You are right DiamondJohn, I should have added "FYI". I will do that next time.

(this post is also "FYI")

As for NFC in RisingOS, I can't turn it on or off, it's as "no NFC device".

I tried again after my previous post, I got different results. even with the RisingOS 20230602 build, I can no longer enable NFC. if I set up with Google StockROM, NFC is enabled, and after that I installed/set up crDroid, NFC is still enabled.

For now, this is the situation I have and I will take a closer look at it for a while.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
I wis to apologize I probably came off a little harsh even though I tried not to. Its just that I am a little triggered if people expect (Im lucky as I currently have the min req equipment wise, but more would be better) me to maintain a ROM, which I am not using and dont request any financial support, but i spend way to much time on as it is.

Some ideas to try.

1. Set the device SELinux as Permissive and see if that works differently. It *could* be a simple SELinux block to the hardware. Which would also be easy to fix with a boot script or even a one line code change to aded to my list of TODO before compiling the ROM.

2. Try different methods to make the switch. (while permissive, its got the best chance, and the logical failures are still logged in the logcat,l that they would of failed if enforcing)

a quick Tile (does it allow you to add? that may imply it knows it has NFC)

Using the settings

Using a app that depends on NFC. Mine pops up a message box if it is off, and takes you to the setting location. More advanced apps may set it themselves. But I would guess security in Android may disable that

Not certain, but I think in crDroid, when I first boot, NFC & Bluetooth are switched on by default.

All the above.

My first reaction is that it is something weird in Rising OS, as the NFC code is sitting in the device tree, which is the same for both RisingOS & crDroid in my build, as they are both "TheMuppets" device trees (ie hardware code)

Another thing you could try if you really wish to cover every base. I was looking at crDroid (I use the same device tree code) and one of the last commits (changes) was to upgrade the device to May's firmware release of blobs (binary device code from Google). So, it may have slightly different drivers / interface / integration to other releases. See the top of the list.

Commits · TheMuppets/proprietary_vendor_google_sunfish

Contribute to TheMuppets/proprietary_vendor_google_sunfish development by creating an account on GitHub.

github.com

So the code would expect the May release of drivers from google.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
Thanks for your information/recommend DiamondJohn.

I have tried many methods, including the method you taught me, but have not been able to resolve (or work around) the "NFC unavailable (= cannot ON/OFF)" issue with RisingOS.

StockROM (May.2023 and June.2023) no problem at all.

crDroid v9.5 (DiamonJohn build, AperioOstendo build) also no problem at all.

RisingOS 20230602 build and 20230617 build both have "NFC unavailable".

I also checked SELinux Permissive but it was not resolved.

I remember that the RisingOS 20230602 build should not have had NFC issues before,

so why is it not working now...?

Maybe (surely) I'm remembering wrong or I'm doing something wrong...

I have no idea.

I would like to take some time to cool down my head, heart and Pixel4a.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
@klazyStrida I think you may be mixing ROMs, which makes it confusing. RiceDroid & RisingOSS are 2 different ROMs. PS: in the back end, they call themselves RisingTechOSS

If the switch to turn on NFC is enabled somewhere, clear your logcat, turn on NFC and take a logcat (ie try to minimise the length). If there is no enabled switch, search for a shell command to do it.

I just checked the device specific code difference in sources between crDroid & RisingOSS ROMs. They use the same device definition (which is where the NFC code resides), BUT they use different different kernels.

Remember, this build is all unofficial no real officially certified or instructions on the way it "should be" built, so I used the LineageOS Kernel as a safe bet for RisingOSS and the crDroid kernel for crDroid, as it had a specific one for our device/CPU, for obvious reasons. As a long shot, maybe there is something in the kernel that is breaking it in RisingOSS but allowing it to work in crDroid.

They may be interchangeable, If I was to change the RisingOSS kernel to use the crDroid specific kernel, and it compiles without requiring any changes (ie my time & effort to fix it), would you be willing to test that? I am guessing yes.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Actually, just noticed there are NFC *DRIVERS* in the kernel...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
Thank you very much.

If you can provide it, I will definitely try it.

I understand that you are focused on crDroid.

I am concerned that it will interfere with that.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Quick update. I tried a few passes, and they failed. I then tried a blank pass the same as before, and it to failed! So, some change in the device tree is misaligned with recent changes to RisingOS. I quickly then went and checked I could still compile crDroid, and it failed on the first new attempt. It turned out to be a simple permission thing caused by how I copied the files over from my Win PC to the linux Vbox. But I thought I did it the same as before. I may give it another go in a week, in case some fixes come in making it compatible again with our device tree.

Regarding NFC not working, which base firmware did you start on? I think you need the May firmware to get the correct radio & bootloader firmware, which could affect its integration with NFC hardware. You can follow the same steps as for the last crDroid build.

https://xdaforums.com/t/rom-unoffic...crdroid-v9-5-with-gapps.4593649/post-88663897

Also, a more generic question., What do you prefer with this ROM over crDroid? am I missing something?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
I'm very sorry for the trouble I have caused you.

My base for trying RisingOS and crDroid is May.2023 firmware.

Before trying crDroid/RisingOS, I flash the May.2023 firmware to both A/B slots every time.

The (like/dislike) comparison between crDroid and RisingOS is very difficult to answer.

One is that I use RisingOS v1.1 on my regular Pixel 6a, and in situations where I have to switch to a spare Pixel 4a, I feel a little more comfortable with the same OS.

I've also used crDroid on another device when it was Android 8/9/10 and have a very good impression of it. That impression has not changed at all now on v9.5, including the simple and well organized customization items.

I don't think there is a big difference in terms of functionality.

As for the UI, I think RisingOS seems a little more sophisticated and easier to use.

At least at this point, there is absolutely no reason to say "it has to be RisingOS".
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
No problems, Im a big boy, I did it to myself. I used to leach ROMs, now i pay it back a little.

crDroid has recently gone alpha for their next release, and have also upgraded to June's firmware. There are code check-in's all day long. Meanwhile, Rising is pretty quiet. Check both their GitHub's (ROM urls would be in the OP's)

Every Android upgrade, I re-evaluate which ROM is the one for that version of Android. You have no reason to be "loyal" to any, you should do the comparison. I have flipped between ROMs on nearly every upgrade. They come and go, rise and fall. I would not get too hooked on stickling to a ROM brand through versions of Android; I have been through too many to count, and some are now dead. A few years ago, I built a few ROMs for the one device, inc crDroid & Resurrection Remix. To me, RR had soooo many more features, BUT everyone else seemed to be hooked on crDroid. But no-one could actually give me a reason apart from previous experience with crDroid (I did kang a brilliant CPU gov dev'ed by the main crDroid guy back then, into my RR & crDroid builds; neobuddy98 is still with crDroid). I didn't like crDroid back then as compared to RR, but today, for the P4A it looks to be in the sweet-spot. That's why I have been building ROMs, to check them/evaluate which one to move into. I did a Bliss (the official is behind the latest), then Rising & then crDroid. The only one I think I really should of also checked was Evolution X (I think it is built by the guys who were behind RR)

For *me*, the sophistication is keeping some familiarity with previous version of Android, not changing as much as one can, with no clear benefit. eg. I personally find the images at the top of the settings app a wasted area.

I guess I see the same I saw previously with people preferring crDroid over RR, now its RisingOS over crDroid. Rising has more total downloads; but crDroid is catching up.

crDroid appears to have more features, it's currently being heavily dev'ed, and you have an unofficial builder for your device, personally soon to move onto crDroid, who is going to look after his own interests. ie ME! Its the one for me, but also if I was simply a user.

The thing I *personally* prefer about crDroid over Rising, is that at first glance, and at the interface, track closer to AOSP & previous ROMs. Where as rising seemed to have gone down a different path.

By the way, I did a test build (haven't flashed it) with two (maybe three) new IO govs of TripNDroid and Kyber. I tried to add Anxiety, ZEN, Maple, SIO, FIOPS, but they are going to need much more work.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
I have not been so strict in comparing ROMs. I installed the ROMs that interested me, and if there was no noticeable problem and it felt good, I would continue to use it.

I think crDroid is a long-lasting project, and it continues to be so because it is so appealing.

Even if the generation of Android changes, there is no major change in the base UI/UX, and there is a sense of security that "the usual crDroid that I am used to using is there. I think there is a good reason why the project can continue for a long time.

I forgot to report one thing.

This week, I experimentally installed LineageOS 20.0 on my Pixel 4a to see how it works.

LineageOS 20.0 20230622 nightly build

MindTheGapps 13.0.0 20230408

Magisk 26.1

SafetyNet fix v2.4.0-MOD1.3

LSPosed v1.8.6 zygisk

AOSPMods Xposed v2.9.0

There are no problems, and NFC(which I was a little concerned about) is working fine.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
crDroid are soon to do another major release, and code changes are happening all day long. RisingTechOSS on the other hand, hasn't had its last commit last week (17th June).

When you say NFC is working fine, how did you test it? I noticed that NFC on my crDroid read my security fob, but didnt read my credit card. It beeped, but the data was blank. Im sure my phone used to read credit cards a few years back. I dont use NFC on my phone, so Im not concerned, I did read on the crDroid Telegram channel that NFC isnt working, but it appears it may on my device.

Also, you say you are using MindTheGApps. How did you flash that after the ROM?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
As for NFC operation, I have confirmed the following at this time

NFC can be turned on/off (QS Panel and Setting/Connected Devices)

CreditCard can be registered in Google Wallet.

CreditCard registered in Google Wallet can be activated.

Actual in-store payment has not yet been confirmed.

MindTheGapps was installed with sideload immediately after LineageOS itself was installed with sideload.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Thats unexpected, I did not think that we could sideload GApps AFTER flashing the ROM. I was under the belief that we can not append flashed components, to our read only partitions on a Pixel 4A 4G.

That could mean I can build non-gapp included versions, and people can choose which level of GApps they wish for. I think I need to find a small component app that is installed by sideload, and test it for myself. Anyone got any ideas of an app that is installed to the system via ADB sideload?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] chozendroid:
If you recall, this is what I was requesting with your CrDroid build a few weeks back. However, since your installation instructions currently use Fastboot instead of ADB sideload, I doubt it would work the same way it does for other ROMs that use ADB. If you are able to convert your build to being ADB-compatible, I'm pretty sure it would be much easier for you as well as those of us that have different Gapps preferences, since we'd be able to just sideload whatever GApps we want on top of the vanilla build of ROM itself.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] klazyStrida:
In fact, I simply followed the LineageOS installation guide without any technical background information.

Install LineageOS on sunfish | LineageOS Wiki

wiki.lineageos.org
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
That is exactly why it stuck in my mind. I asked if you were sure, but you backed off. And to be honest, I still want to see it for myself, and hence I asked for any examples of a small add-on using fastboot. I dont wish to flash my device too often.

As to using fastboot for the initial installation, I dont think that would change the ability to sideload later. I would not expect it to care how the initial installation was. A flashed partition is a flashed partition. I *think* I still have a first initial build attempt without GApps floating around my HDD.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
yeah, I briefly read those also after reading your post.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] chozendroid:
I will admit I don't fully understand all the inner mechanisms of how the partition structure and the minor nuances of how the build/flashing process works, so I prefer not to try to push for things that I don't fully understand... especially if it could come across as being a nuisance to the developer(s).

Even though it's an older build, I wouldn't mind giving it a try sometime between now and the weekend if you wanna make it public alongside your current build
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Im ALL for respectful discussions. I often learn by being pointed out where I am wrong (and it happens pretty often!), and am grateful when it happens. I would of hoped I came across as that. But for certainty, I understand it could come off as being annoyed. sorry.

I wouldnt push it publicly, more likely in a PM. It would just take time & space to upload it, both of which are a limited commodity.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] chozendroid:
That's cool. Whatever works for you is fine by me 👍🏾
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Marcia8246:
i have tried many times to install this rom, but not understand my error...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AlexKarimov:
You're using powershell? I've never done that to flash a rom. Use command prompt. In the folder with fastboot and the rom files, type cmd in the address bar, this will open a command prompt. Use that instead

EDIT: after looking at your posts, you seem to flash a lot. Do you clean flash to stock in between roms? That would be my next suggestion. Also, make sure your platform tools is up to date and drivers are the proper ones.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Marcia8246:
i have tried, but ...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Marcia8246:
sies, clean flash after latest stock firmware update
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AlexKarimov:
You need to make sure you're opening the command prompt in the same folder where adb and the rom files are. If you're doing that, try this next:

Type the following in a CMD prompt

set ANDROID_PRODUCT_OUT = c:/(location of the folder in which you have platform tools installed)

If that doesn't work, try finding another version of platform tools. There are reports that Google replaced the working platform-tools 34.0.1 release with a broken one. Try using 33.0.3 for the time being
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Marcia8246:
i have tried with 33.0.3 version, but still the same message, its so frustrating!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AlexKarimov:
What about the commands I told you to use, did you try that? What was the result? Are the rom files in the same folder as fastboot and are you opening the command prompt in there? Please answer all of these questions
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Marcia8246:
1 yes, but same result, 2 yes rom zip are in the same folder of adb platform 3 i have open cmd in address bar inside the platform tools folder, sorry for my bad english, and thanks a lot for your patience
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AlexKarimov:
Then I'm out of ways to help you, I'm sorry.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Any test pilot for a test build of ALPHA of v1.2-Caspium?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Hecker007:
Me
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Ya missed da boat!

They are in a stage of really heavy dev, so the build from a few days ago, is almost of no value as compared to the latest source. So im not comfortable releasing that "old" build.

Last week, just before i did the build, the source was "broke" / missing an integral part, but it came back, and also a build I attempted a few days before failed (also bad source). It was really a confirmation that my build process still works, and it does, so hopefully I'm ready when it moves at least to BETA or even release of official builds of v1.2; but remember, this is not a build I use, so no promises of future builds.

I was a little surprised you stepped up, I didnt think you had a Pixel 4A specifically, just a "Pixel" of some form.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
NEW BUILD - risingOS-v1.2-Caspian-202307130450-sunfish-GAPPS-UNOFFICIAL-DiamondJohn.zip

See OP for download

And remember, I dont test flash this ROM as I am all about crDroid.

Changelog is borked in the build (I think its RisingTechOS issue), so see attached for the changelog.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Hecker007:
I'm getting error when installing.

I gave the following command

fastboot update -w risingos....zip

zip missed a central dir sig (at 0)