Unofficial CrDroid-OSv6 Android 10

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,498
3,557
243
Sydney
Don't know if your interested, but here are some SELinux denials. I have not filtered the list, but some are happening many times.

https://hastebin.com/viramupovo.shell


Also, I assume you are more interested in our device specific issues. Where would you suggest to post issues that would be general to the ROM, and most likely an issue with all devices?
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,498
3,557
243
Sydney
Finally got around to installing this new build.:highfive:

However, I went through a boot loop on the boot animation:crying:, so I tried again without gapps, and it booted.:victory:

So, I am now just recharging to give it another flash, but this time, I will not be using OpenGApps (open_gapps-arm-10.0-nano-20200129.zip). I think last time (when it worked) I used BiTGApps-arm-10.0.0-v0.6_signed.zip.:fingers-crossed:
 

devnotname

Member
Mar 14, 2019
31
1
8
When I installed 5 or more applications, open an music player, drag the status bar down to have 1 latency, sometimes reboot SystemUI
 
Last edited:

Alienns

Senior Member
May 13, 2013
137
25
0
Belgrade
Hello,
I make Full wipe nstalled build 2020-02-09 + pico gapps than update to build 2020-02-20. But my charging still is extremely slow. See screenshot. I tried 3 usb cables, it`s same and phone is hot. Also battery was charging great in old Lineage 16 rom. Do i need to flash some other bootloader?
edit: usual charge is around 0.9A, now phone does not charge at all, even connected on charger slowly dropping down and when phone is OFF does not charge at all. 0.00A

btw. Rom working excellent this 2 days i`m using it.
 

Attachments

Last edited:

devnotname

Member
Mar 14, 2019
31
1
8
update package 20200220 has failed to access internal storage,
I have not returned to package 20200209 and package 20200209 does not contain this error
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,498
3,557
243
Sydney
Some issues with latest

I understand @khalvat is mostly working with getting crDroid to specifically run on our device, and the issues I raise are commonly with crDroid code, and not code specific to our device (but some may be S4 specific). However, by posting here, when I find the place to report the issue, I can always link back to here.Which is why I kept them as separate posts instead of combining all into one.

Firstly, I am getting the following SELinux denials
Code:
# 02-27 22:23:50.884   346   346 E SELinux : avc:  denied  { add } for interface=vendor.qti.hardware.cryptfshw::ICryptfsHw sid=u:r:hal_keymaster_qti:s0 pid=25888 scontext=u:r:hal_keymaster_qti:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
allow hal_keymaster_qti default_android_hwservice:hwservice_manager {  add  };

# 02-27 22:24:01.820   346   346 E SELinux : avc:  denied  { add } for interface=vendor.qti.hardware.cryptfshw::ICryptfsHw sid=u:r:hal_keymaster_qti:s0 pid=25917 scontext=u:r:hal_keymaster_qti:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
allow hal_keymaster_qti default_android_hwservice:hwservice_manager {  add  };

# 02-27 22:25:01.533   346   346 E SELinux : avc:  denied  { add } for interface=vendor.qti.hardware.cryptfshw::ICryptfsHw sid=u:r:hal_keymaster_qti:s0 pid=25939 scontext=u:r:hal_keymaster_qti:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
allow hal_keymaster_qti default_android_hwservice:hwservice_manager {  add  };

# 02-27 22:26:03.437   346   346 E SELinux : avc:  denied  { add } for interface=vendor.qti.hardware.cryptfshw::ICryptfsHw sid=u:r:hal_keymaster_qti:s0 pid=25941 scontext=u:r:hal_keymaster_qti:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
allow hal_keymaster_qti default_android_hwservice:hwservice_manager {  add  };

# 02-27 22:26:08.496   346   346 E SELinux : avc:  denied  { add } for interface=vendor.qti.hardware.cryptfshw::ICryptfsHw sid=u:r:hal_keymaster_qti:s0 pid=26067 scontext=u:r:hal_keymaster_qti:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
allow hal_keymaster_qti default_android_hwservice:hwservice_manager {  add  };

# 02-27 22:26:13.392   346   346 E SELinux : avc:  denied  { add } for interface=vendor.qti.hardware.cryptfshw::ICryptfsHw sid=u:r:hal_keymaster_qti:s0 pid=26141 scontext=u:r:hal_keymaster_qti:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
allow hal_keymaster_qti default_android_hwservice:hwservice_manager {  add  };

# 02-27 22:26:18.373   346   346 E SELinux : avc:  denied  { add } for interface=vendor.qti.hardware.cryptfshw::ICryptfsHw sid=u:r:hal_keymaster_qti:s0 pid=26235 scontext=u:r:hal_keymaster_qti:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
allow hal_keymaster_qti default_android_hwservice:hwservice_manager {  add  };

# Execution Time: 10.415 seconds
# Produced at: 2020-02-27 22:26:28
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,498
3,557
243
Sydney
Bug in crDroid settings

So, when you first go into the crDroid settings, it all looks good.
Screenshot_20200227-212933.jpg

But if you scroll to see further down, the settings start to overlap with the titles.
Screenshot_20200227-212945.jpg
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,498
3,557
243
Sydney
Unused Clickable area - feature request

In previous versions of android, if you click on the battery image, it will take you to the battery history. In this ROM, it does nothing, so is wasted, and you are forced to go to the menu to get to the history.
Screenshot_20200227-212909.jpg
 
Last edited: