Radxa RockPi 4 RK3399 - Custom Android Pie firmware by mo123

[RiCkLaR_atvX]

The latest firmware is actually v1.5, I updated the OP now.
I'm working on v1.6 now, the version number might have been a mishap since I did v1.6 for the Khadas Edge RK3399 also at a similar time.

Ok, download version 1.5 and hope to give it a try this week.

The framebuffer is 1080p so that is correct. If you set the resolution to 4K then it will be upscaled from 1080p but video playback that uses a different layer will still be done in 4K.
The Nvidia Shield is currently the only Android device that can display both the UI and video playback in 4K.

Ok, but if the framebuffer can be set at 60hz and not 30hz then that would be optimal. Using apks like DevCheck and DeviceInfoHW both show the default of 30hz which they are getting info from reading the devices framebuffer I am guessing.

Thanks for the tip about SettingsIntelligence. I didn't know it had any use.

I should have typed '/system/priv-app/' as the location Not '/system/app/' in the post above, but I am sure you knew that.

Vulkan is supposed to already be working.

Vulkan may be activated in the kernel stack but not in android, my first test was to check DevCheck app and it said NO for Vulkan supported device. So sorry if you looked at my Pictures of the 3dMark benchmark and it shows Vulkan was tested accurately, those screenshots were taken after I hacked in the missing Permission files to activate Vulkan in android. Please test as well, I believe that the game Asphalt 9 can only be download from Google Play Store if the device has Vulkan activated in Android.

For the display problem
Can you go through all the Display resolutions and apply them in TvSettings?
Make sure each resolution you apply stays checked and the selected item doesn't jump to a previous resolution.
If so, there might be a timing difference with the tv's edid info compared to the values I added based on my tv.
You can then delete the /system/usr/resolution_whilte.xml file(root access needed) and it will use timings based on your tv but there will be lots of extra resolutions like interlaced ones and PC monitor ones that are useless for a tv. or you can continue using the file but remove all the 4096x2160p entries in the file so Android will only use 3840x2160p resolutions that is supported up to 60hz, 4096x2160p is only supported up to 30hz. You can also use a startup script to force Android to start in any resolution and frame-rate, I'll check if I can find it.

Yes, deleting the 4096x2160p entries did help. Also, I think my main problem/conflicts were with RefreshRate app and SmartYouTube, my solution was to not use the RefreshRate app and to also not use the Autoframerate settings in SmartYT app. The problems with SmartYouTube are the apks fault and not the ROM, Vanced YouTube worked without any issues and/or switching to 4k videos, which SmartYouTube had errors with several different 4k videos at 4k resolution.

[mo123]

So, this is going to be a long post...


First Impressions and Notes :

- 1st Forum Post "Changelog" says v1.4 - when in fact the version I downloaded and installed is v1.6 according to About section of settings.
- Magisk works great and installed correctly the latest Update.
- TWRP seems to be an Older version and could use a version update. Currently it would not detect the System partition or allow it to be mounted correctly to flash zips. Tried to install my (apk+data) backup from Migrate and failed.
- Busybox is older version. Yes, Magisk has the most current version 1.31.1 install-able as a Module, but it would be nice if that was included and installed in the ROM system build.
- Bonus a lot of apps I have never heard of, some from APKpure so they can be updated in that app, but of course the best addition to the ROM is Dashboard which is absolutely phenomenal.
- HeadsUpNotifications app, definitely needs the user to go through the settings to set it up correctly.
- Device uses a Xiaomi Fingerprint in build.prop -- does this help with device registering itself with Google on first boot? I have noticed Superceleron doing the same thing in his ROMs.
- Does 'WifiDisplay' app work for you? Noticed that it is the very old version that hasn't been updated by Rockchip in years. Couldn't get it to work with different devices, so just uninstalled it from the Rom.
- Lightning Browser has an available update to 5.1.0 but the current version 4.4.2.93 must have a different Signature blocking it from being updated. Would it be possible to use Bromite as the installed system browser instead? Check https://bromite.org
- Did not understand what purpose the "Settings > Tuner Settings > Home Screen > Default setting" had, it is not possible to permanently change launchers inside ATV ROM.
- My display registers as 4096x2160p in apps like Aida64, but when you check default settings the device always reverts to 1920x1080p30hz or to a viewport of the same default 1920x1080p30hz even after changing the setting and/or rebooting.
- ROM uses the <interactive> CPU Governor, I prefer to use the <ondemand> CPU governor, if I was using a forced-air cooling and didn't mind the extra wattage used then of course <performance> governor would be best.

Bugs :

- Bug where you exit the current App when you Allow/Deny Permission Dialog prompt. Known bug with Android 9, but it is still SO annoying.
- Bug/Crash in <More Settings> when selecting <Accessibility> and <Display> -- both will not open and send you back to TVsettings.
- Performance Dialog ~ Ram showing "-264mb Total" and not showing Usage or Quantity. Kodi 19 also had problem identifying Ram quantity.
- Search in 'More Settings' doesn't work, fix is to include AOSP '/system/app/SettingsIntelligence/SettingsIntelligence.apk' in ROM build.
- Secure Setting display_density_forced is set at 240. Switching this by terminal to the correct ATV standard of 320 gets reset to 240 after Reboots or Shutdown.
- Bug where "Developer Option > Smallest Width" always reverts to 540p, for my 4k TV it looks best at a setting of 720p

Suggestions an Speculations :

- Add AOSP-Clock aka DeskClock.apk or GoogleClock as '/system/app/' so that have option to use clock as a Screensaver.
- Can delete system apks BasicDaydreams and PhotoTable from '/system/app/' -- both are not needed.
- Kodi is 19.0-Alpha, I would prefer the current stable release of 18.6 be included in the ROM, leave 19.0 for the LibreELEC Nightly+Development users until it is stable release for Android.
- Delete the old Rockchip FileExplorer <com.android.rockchip> -- and install an ATV-type file manager like "FileExplorer" by Anker or ever just add "Files" by Google in its place.
- Can Vulkan be activated in the ROM? The ARM-Mali site says the GPU supports Vulkan API
- I suspect that if the ROM had the AOSP Gallery.apk installed in '/system/app/' that it would be possible to have a wallpaper installed and visible in Overview/Recents window. I believe it is a required system app to mount a wallpaper. But of course, the wallpaper won't be visible on the home screen because of ATV restrictions.

• Settings {system,secure,global} that should be set by Default, maybe they already where set, but I went ahead and inserted them thought terminal, here is edit:

settings put system enable_pass_through 1
settings put system font_scale 1.25
settings put system haptic_feedback_enabled 0
settings put global heads_up_notifications_enabled 1
settings put global development_settings_enabled 1

Cheers!!!

Thanks for the detailed review.

The latest firmware is actually v1.5, I updated the OP now.
I'm working on v1.6 now, the version number might have been a mishap since I did v1.6 for the Khadas Edge RK3399 also at a similar time.
Magisk updated, so I will include the new Manager.
In v1.5 there were lots of changes to TWRP, so I think it will mount all the partitions correctly now.
I will just have to figure out how to include the new busybox, not sure from where the old one comes from.
The Xiaomi fingerprint is supposed to offer better app compatibility, but I haven't noticed differences with it on, you still need to use Magisk.
Google apps can work correctly with it excluded.
WifiDisplay works, you also need to enable Wireless Display in your phone's display settings, there is also a CastReceiver app that does the same some users include in roms but I think it's a modded app since the one on the Play Store is time limited.
Bromite can work, the only problem is preinstalled apps take twice their storage space, including their extracted files since Android Pie on Rockchip devices, so 200MB extra.
The framebuffer is 1080p so that is correct. If you set the resolution to 4K then it will be upscaled from 1080p but video playback that uses a different layer will still be done in 4K.
The Nvidia Shield is currently the only Android device that can display both the UI and video playback in 4K.
Interactive performs better than on-demand for scaling from low to high cpu usage but I can make an on-demand boot.img later.

Bug where you exit the current App when you Allow/Deny Permission Dialog prompt. Known bug with Android 9, but it is still SO annoying
- Fixed now in v1.5
Will check the other issues, the ram usage worked correctly in the past I think.
Thanks for the tip about SettingsIntelligence. I didn't know it had any use.
Will check the display densities, it was changed to 320p but something might still trigger or change it.

Will test a few file managers, most have adware or limited free features but a simpler app optimised for tv can do.
Vulkan is supposed to already be working.


For the display problem
Can you go through all the Display resolutions and apply them in TvSettings?
Make sure each resolution you apply stays checked and the selected item doesn't jump to a previous resolution.
If so, there might be a timing difference with the tv's edid info compared to the values I added based on my tv.
You can then delete the /system/usr/resolution_whilte.xml file(root access needed) and it will use timings based on your tv but there will be lots of extra resolutions like interlaced ones and PC monitor ones that are useless for a tv. or you can continue using the file but remove all the 4096x2160p entries in the file so Android will only use 3840x2160p resolutions that is supported up to 60hz, 4096x2160p is only supported up to 30hz. You can also use a startup script to force Android to start in any resolution and frame-rate, I'll check if I can find it.

[RiCkLaR_atvX]

So, this is going to be a long post...
1st want to start this post with a BIG THANK YOU to mo123 for this ROM. It is absolutely amazing and feels like a production ROM, at least 100% better then what any Chinese Manufacturer is releasing in their TV boxes. If I were to give this ROM a rating it would be 90% on the way to being exceptionally Great. My quibbles an quirks found in the Rom are all relatively small.

My setup is 4gb Ram Rock Pi 4 B with 32gb emmc storage in an aluminum case with passive cooling large heatsink.

• ROM Benchmark testing :

Did achieve 112K high score benchmark on very first test when device was cold and before adding my full suite of apps, but after several other tests device now always averages 109K score with Antutu version 8.3 :


Geekbench4 :


Storage and Ram test with A1 SD Bench :

3DMark :



First Impressions and Notes :

- 1st Forum Post "Changelog" says v1.4 - when in fact the version I downloaded and installed is v1.6 according to About section of settings.
- Magisk works great and installed correctly the latest Update.
- TWRP seems to be an Older version and could use a version update. Currently it would not detect the System partition or allow it to be mounted correctly to flash zips. Tried to install my (apk+data) backup from Migrate and failed.
- Busybox is older version. Yes, Magisk has the most current version 1.31.1 install-able as a Module, but it would be nice if that was included and installed in the ROM system build.
- Bonus a lot of apps I have never heard of, some from APKpure so they can be updated in that app, but of course the best addition to the ROM is Dashboard which is absolutely phenomenal.
- HeadsUpNotifications app, definitely needs the user to go through the settings to set it up correctly.
- Device uses a Xiaomi Fingerprint in build.prop -- does this help with device registering itself with Google on first boot? I have noticed Superceleron doing the same thing in his ROMs.
- Does 'WifiDisplay' app work for you? Noticed that it is the very old version that hasn't been updated by Rockchip in years. Couldn't get it to work with different devices, so just uninstalled it from the Rom.
- Lightning Browser has an available update to 5.1.0 but the current version 4.4.2.93 must have a different Signature blocking it from being updated. Would it be possible to use Bromite as the installed system browser instead? Check https://bromite.org
- Did not understand what purpose the "Settings > Tuner Settings > Home Screen > Default setting" had, it is not possible to permanently change launchers inside ATV ROM.
- My display registers as 4096x2160p in apps like Aida64, but when you check default settings the device always reverts to 1920x1080p30hz or to a viewport of the same default 1920x1080p30hz even after changing the setting and/or rebooting.
- ROM uses the <interactive> CPU Governor, I prefer to use the <ondemand> CPU governor, if I was using a forced-air cooling and didn't mind the extra wattage used then of course <performance> governor would be best.

Bugs :

- Bug where you exit the current App when you Allow/Deny Permission Dialog prompt. Known bug with Android 9, but it is still SO annoying.
- Bug/Crash in <More Settings> when selecting <Accessibility> and <Display> -- both will not open and send you back to TVsettings.
- Performance Dialog ~ Ram showing "-264mb Total" and not showing Usage or Quantity. Kodi 19 also had problem identifying Ram quantity.
- Search in 'More Settings' doesn't work, fix is to include AOSP '/system/app/SettingsIntelligence/SettingsIntelligence.apk' in ROM build.
- Secure Setting display_density_forced is set at 240. Switching this by terminal to the correct ATV standard of 320 gets reset to 240 after Reboots or Shutdown.
- Bug where "Developer Option > Smallest Width" always reverts to 540p, for my 4k TV it looks best at a setting of 720p

Suggestions an Speculations :

- Add AOSP-Clock aka DeskClock.apk or GoogleClock as '/system/app/' so that have option to use clock as a Screensaver.
- Can delete system apks BasicDaydreams and PhotoTable from '/system/app/' -- both are not needed.
- Kodi is 19.0-Alpha, I would prefer the current stable release of 18.6 be included in the ROM, leave 19.0 for the LibreELEC Nightly+Development users until it is stable release for Android.
- Delete the old Rockchip FileExplorer <com.android.rockchip> -- and install an ATV-type file manager like "FileExplorer" by Anker or ever just add "Files" by Google in its place.
- Can Vulkan be activated in the ROM? The ARM-Mali site says the GPU supports Vulkan API
- I suspect that if the ROM had the AOSP Gallery.apk installed in '/system/app/' that it would be possible to have a wallpaper installed and visible in Overview/Recents window. I believe it is a required system app to mount a wallpaper. But of course, the wallpaper won't be visible on the home screen because of ATV restrictions.

• Settings {system,secure,global} that should be set by Default, maybe they already where set, but I went ahead and inserted them thought terminal, here is edit:

settings put system enable_pass_through 1
settings put system font_scale 1.25
settings put system haptic_feedback_enabled 0
settings put global heads_up_notifications_enabled 1
settings put global development_settings_enabled 1

Cheers!!!

[Silver]

Hope u still work on the full android firmware mo123 , rly like your work for rock-chips, would love to beta test the rom,

i still have my X99 box lying around with rk3399 i was able to root it but its overall full of bugs and no autoframerate switching in RKMC/FTMC otherwise great power with rk3399 cant compete rk3328 cpu. Are you able to include OC settings in the kernel that i mentioned above?

greets

[lliou]

@mo123,

Tried frist one and worked !!!
You are so cool !!!
Do you still working on full Android version ?

[mo123]

@mo123,

Many thks for reply promptly
well... What I can do now is waiting for your new version.

Please test 1.4 firmware for sdcard booting troubleshooting
Newer u-boot(also has nvme changes)
Also test this one on nvme(for people that use nvme storage)

https://mega.nz/#!BVdTVKCZ!tqbdgOh8PdEg36vq3rrd_eBjrD16K0QqqKAi7riD3iQ

Older u-boot
https://mega.nz/#!oFExhKZJ!YneWFMSVbbLltVEZ5HzoPoqllvuxByVMGylgh0q 3U0U 1

If the 1t one is not booting, try the 2nd one.

[lliou]

I have v1.3 on emmc and put v1.4 on a micro-sd card and it boots properly.
But some users also say just v1.4 micro-sd card booting has some problem.
It might be because I added USB booting, it seems USB booting only works if firmware is flashed to emmc, then you can use the bottom USB 3.0 port for LibreELEC/Armbian.
So I hope to get a newer u-boot in future so you can use any booting method easily.

@mo123,

Many thks for reply promptly
well... What I can do now is waiting for your new version.

[mo123]

@mo123,

Tried boot Ver.1.4 on from, but stuck at RockPi first screen
tried again with another SSD, still same
(Ver. 1.2 worked fine before)
Still have to say many thks for your great effort !!!

I have v1.3 on emmc and put v1.4 on a micro-sd card and it boots properly.
But some users also say just v1.4 micro-sd card booting has some problem.
It might be because I added USB booting, it seems USB booting only works if firmware is flashed to emmc, then you can use the bottom USB 3.0 port for LibreELEC/Armbian.
So I hope to get a newer u-boot in future so you can use any booting method easily.

[lliou]

@mo123,

Tried boot Ver.1.4 on from, but stuck at RockPi first screen
tried again with another SSD, still same
(Ver. 1.2 worked fine before)
Still have to say many thks for your great effort !!!

[Silver]

Still working on full android rom for the device?

waiting for it so i can flash my rockpi to use for home multimedia

[mo123]

nu.nav.bar added to v1.4 firmware.

[mo123]

Youtube Vanced added to v1.4 firmware.

[mo123]

Updated OP with v1.3 & v1.4 firmware info.

[Silver]

Is it supposed to happen? i have red led blinking on my 1.3V of the board

[Silver]

The flash options is really nice feature of the rom