ROM AOSP Android 9.0 Pie + Android-TV version

[secuflag]

Hi all,
I would like to share my ROM based on latest sources from hardkernel, codewalkerster and AOSP.
The goal of this ROM is speed and stability.


Main features:

• Android 9 Pie - Release 46 (PQ3A.190801.002)
• Android security patch level: January 2022
• Kernel 4.9.303
• OpenGapps (pico variant)
• Google Chrome
• Google WebView
• WireGuard VPN module
• Customizable Launcher3
• RMSettings:
  • Statusbar: Network monitor
  • Statusbar: Clock and Date customizations
• Extra Tile (VPN, Expanded desktop, Compass, USB tether)
• Expanded Desktop
• Eleven music app from LineageOS
• Hosts file with AD block
• ...and more!

Changelog:

Code: Select all

15 Nov 2022 - PIE-R.23.3
- Merged latest changes from HK
- Updated SQLite to v3.39.4
- NTFS-3G 2022.10.3
- Minor fixes, updates and improvements

29 Jul 2022 - PIE-R.23.2
- Merged latest changes from HK
- Updated SQLite to v3.39.2
- Updated NTFS-3G to v2022.5.17
- Minor fixes, updates and improvements

28 Feb 2022 - PIE-R.23.1
- Fixed root access on ATV

27 Feb 2022 - PIE-R.23
- Merged latest changes from HK
- Updated Kernel to v4.9.303
- Updated SQLite to v3.38.0
- Minor fixes, updates and improvements

10 Feb 2022 - PIE-R.22
- Merged Android security patch: January 2022
- Merged latest changes from HK
- Updated Kernel to v4.9.300
- Minor fixes, updates and improvements

10 Dec 2021 - PIE-R.21
- Merged Android security patch: December 2021
- Merged latest changes from HK
- Updated Kernel to v4.9.292
- Updated NTFS-3G 2021.8.22
- Minor fixes, updates and improvements

7 Oct 2021 - PIE-R.20
- Merged Android security patch: October 2021
- Merged latest changes from HK
- Updated Kernel to v4.9.285
- Minor fixes, updates and improvements

18 Sep 2021 - PIE-R.19.1
- Fixed updatepackage script

16 Sep 2021 - PIE-R.19
- Merged Android security patch: September 2021
- Merged latest changes from HK
- Updated WireGuard 1.0.20210606
- Updated Kernel to v4.9.282
- Updated SQLite to v3.36.0
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

11 Apr 2021 - PIE-R.18
- Merged Android security patch: April 2021
- Merged latest changes from HK
- Added 'nano' text editor
- Updated kernel to v4.9.266
- Updated SQLite to v3.35.4
- Fixed issue with vold
- Fixed issue with Gboard updates on ATV
- Restored EXT4 fs in userdata partition 
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

6 Mar 2021 - PIE-R.17
- Merged Android security patch: March 2021
- Merged latest changes from HK
- Updated kernel to v4.9.259
- Updated SQLite to v3.34.1
- Updated Chrome to v88 
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

16 Jan 2021 - PIE-R.16
- Merged Android security patch: January 2021
- Merged latest changes from HK
- Updated kernel to v4.9.251
- Updated SQLite to v3.34.0
- Fixed Google Play Film on ATV
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

12 Nov 2020 - PIE-R.15
- Updated Kernel: 4.9.243
- Updated WireGuard: 1.0.20201112
- Fixed Gboard on ATV
- Fixed missing usb_modeswitch package

11 Nov 2020 - PIE-R.14
- Merged Android security patch: November 2020
- Merged latest changes from HK
- Updated kernel to v4.9.242
- Updated WebView to v86.0.4240.185
- Removed Google Play Music from ATV
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

8 Oct 2020 - PIE-R.13:
- Merged Android security patch: October 2020
- Merged latest changes from HK
- Updated kernel to v4.9.238
- Updated SQLite to v3.33.0
- Updated WebView to v86.0.4240.75
- Updated FFmpeg
- Updated NTFS-3G to v2017.3.23
- PackageInstaller: Show versions when installing or updating packages
- Removed busybox, welcome toybox!
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

26 Jul 2020 - PIE-R.12:
- Merged latest changes from HK
- Updated kernel to v4.9.231
- GCC updated to v10.2 (used to compile kernel)
- Updated SQLite to v3.32.3
- Fixed f2fs related issue in recovery mode
- Updated WebView to v84.0.4147.89
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

29 May 2020 - PIE-R.11:
- Merged latest changes from HK
- Updated kernel to v4.9.225
- GCC switched from v9 to v10 (used to compile kernel)
- Updated SQLite to v3.32.1
- OdroidSettings: Added preference to show GSF ID
- Removed Lawnchain launcher
- Restored Launcher3
- userdata: Migrated from ext4 to f2fs
- Fixed realtek rtl8812au wifi driver connection issue
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

11 May 2020 - PIE-R.10:
- Merged latest changes from HK
- Added Google Files to Android-TV version
- Updated Lawnchair 2 2.1-2621
- Updated Gapps packages - ATV & non-ATV versions
- Minor fixes, updates and improvements

24 Apr 2020 - PIE-R.09:
- Merged latest changes from HK
- Updated Kernel to v4.9.219
- Updated WebView and Chrome to 81.0.4044.111 (To fix this: https://bugs.chromium.org/p/chromium/issues/detail?id=1051705)
- Merged latest changes of rtl8812au driver
- Updated Gapps packages - ATV & non-ATV versions
- Included Lawnchair instead of Launcher3
- Minor fixes, updates and improvements

Download:

• ROM: https://github.com/odroid-dev/android-p ... ses/latest
• Sources: https://github.com/odroid-dev/android_manifest

Google Account:
Before to set up your Google account you must:

1. Open: Odroid Settings -> Misc settings -> GSF ID
2. Take note of your Google Services Framework (GSF)
3. Go to: https://g.co/AndroidDeviceRegistration, login with your Google account and paste the Google Services Framework (GSF) id
4. Wait between 2 to 10 minutes
5. Reboot your board
6. Now you should be able to setup your Google account

Use the remote "OK" button as "Enter" on ATV:

1. Code: Select all

   $ adb root
   $ adb pull /system/usr/keylayout/Generic.kl
   

2. Change:

   Code: Select all

   key 28    ENTER

   with:

   Code: Select all

   key 28    DPAD_CENTER

3. Code: Select all

   $ adb remount
   $ adb push Generic.kl /system/usr/keylayout/Generic.kl
   

4. Reboot

Credits:

• telix.pl for the Android Pie image

Screenshot:
(click to open)

[rooted]

Nice work, how are you liking the C4 so far? Run into any major issues while porting the OS?

[secuflag]

No issue so far! Android runs very smoothly.

[bobrooney]

You must click on this icon, not on the blue one

Hi,

i've tried that with the PIE-R.09 version for the C4 and there is no Files app like in the picture. Could you please help me out here?

And big thanks for your work on the ROM.

bobrooney

[ETAPRIME]

Looks like ATV does not have a files app installed. Am I missing something?

[secuflag]

Looks like ATV does not have a files app installed. Am I missing something?

Yep, I forgot to add it
Download and install latest release.

[secuflag]

First post updated!

Have fun!

[OldGaf]

I have a couple C2's and waiting on my C4.

I have always just used the stock Android that comes with the Emmc and I have never used ATV at all.
Can you tell me what the basic +/- 's are for using ATV?

[mar]

Thanks for Your work,
There is one problem with ATV version for my board.
I can't accept a WiFi password, I type a passphrase and it's impossible to go next, and to connect.
I'm using a Bluetooth keyboard, the onscreen keyboard is not working with mouse.

[secuflag]

@mar: Try with:

Code: Select all

$ adb pull /system/usr/keylayout/Generic.kl

Open it (NOT with Notepad if you are using Windows, use Notepad++ instead) and replace the line:

Code: Select all

key 28    ENTER

with:

Code: Select all

key 28    DPAD_CENTER

Save and close, then push back the file;

Code: Select all

$ adb remount
$ adb push Generic.kl /system/usr/keylayout/Generic.kl

Now reboot the board, you should fix with this.

[secuflag]

@OldGaf: Android-TV it's more easy to use than the "standard" version of Android.

[rooted]

@OldGaf: Android-TV it's more easy to use than the "standard" version of Android.

With a remote

[jayjr1105]

Where is the updated image with the files app installed?

[secuflag]

Not released yet.

[secuflag]

First post updated!

NOTE: This release (R.11) is only available in selfinstall image.
That's because the /data partition must be reformatted from ext4 to f2fs for better performances.
If you don't install this release you will not be able to boot any future release using the updatepackage.

I'm sorry for the inconvenience.

Have fun!

[SACHOMAN69]

Hello, the first thing is to thank you for this great rom and apologize for my English from Google translator, I have tried to install your rom, R11 does not atv through an emmc card but it is impossible for me, it always stays half of the installation and ahy does not happen, I have left it like that for more than 1 hour and it always stays there, I have downloaded the rom several times and I have recorded it several times but it continues and anyway, on a microsd card I had no problems but it is impossible for me in an emmc card
Saludos

[secuflag]

If I understand correctly did you try to install the ATV version on eMMC and failed.

But, you can install it on the MicroSD card, right?
Just to be sure, try to install this image and let me know if works or not: selfinstall-odroidc4-12-64bit-20200522
(Read here if you have some doubt on how to flash image files)

[SACHOMAN69]

Thanks for your help, you have not understood me, the version I tried is the one that is not atv
The atv version if you can install it on the emmc, with the atv version there was no problem installing the image on the emmc
Saludos

[secuflag]

Anyway, try to install the image linked on the post above.

[SACHOMAN69]

Thank you very much for all your help and time, now if the new image starts well, looking forward to seeing the new version of the rom with the fixed start for emmc cards
Saludos

[secuflag]

I just tried to download and install selfinstall-odroidc4.img.xz and works fine, device boots without problem.

What do you use to write image file?

Check the sha1sum of your file;

Code: Select all

4c095a998359753c53ec079eb91e77349c44f896  selfinstall-odroidc4.img.xz

[SACHOMAN69]

It is what I have told you, the new image if it starts very well, the Google translator changes everything jijijijijijiji jijijijijijiji

[secuflag]

Which application did you install? selfinstall-odroidc4-12-64bit-20200522 or selfinstall-odroidc4.img.xz

[SACHOMAN69]

install this image
selfinstall-odroidc4-12-64bit-20200522 And works
Saludos

[secuflag]

That's not my ROM, is the official one from HardKernel.

[SACHOMAN69]

When I have a gap I will, thank you very much for everything
Saludos

[doidgy]

Installed atv_selfinstall-odroidc4.img.xz and works really well.
Had to uninstall updates on play store app.
When clicking on the developer options it goes back to the home page.
I am a real noob at android and am struggling to change the keyboard layout to uk and how to set up a remote control.
I thought there was supposed to be a remote.conf file in the etc folder ?

[secuflag]

@doidgy: Install the Gboard from the Play Store then you'll be able to change keyboard layout.
If you have a CEC compatible device you should be able to use its remote control, or try this https://play.google.com/store/apps/deta ... .tv.remote

[secuflag]

Small teaser, Android 10 (AOSP) running on the odroic4

[SACHOMAN69]

Good but the truth that Android 9 in your rom is very good and it will make me feel heavy that I change your current rom
Saludos

[Beefy1986]

Hey, thanks for getting a great Android TV rom out there for the C4! I'm having 2 issues with the build, and I'm wondering if anyone is seeing the same things.

1. I'm using a Plugable USB Bluetooth adapter, and scanning in Android TV is seeing devices (tried a dual shock 4 and another Bluetooth controller), but pairing fails after a few seconds.

2. I've enabled Developer Options via the normal method, but when I try to enter the actual menu, I just get dumped back to the home screen. Obviously this makes it more difficult to get apps side loaded.

Any ideas?

[secuflag]

1. I'm using a Plugable USB Bluetooth adapter, and scanning in Android TV is seeing devices (tried a dual shock 4 and another Bluetooth controller), but pairing fails after a few seconds.

Can you provide some logs using logcat please?

2. I've enabled Developer Options via the normal method, but when I try to enter the actual menu, I just get dumped back to the home screen. Obviously this makes it more difficult to get apps side loaded.

Thanks, will be fixed on the next release.

[Beefy1986]

1. I'm using a Plugable USB Bluetooth adapter, and scanning in Android TV is seeing devices (tried a dual shock 4 and another Bluetooth controller), but pairing fails after a few seconds.

Can you provide some logs using logcat please?

Here's a logcat (expires in 24 hours): https://privatebin.net/?f251e4c47d9015a ... QBb3aKo61D

2. I've enabled Developer Options via the normal method, but when I try to enter the actual menu, I just get dumped back to the home screen. Obviously this makes it more difficult to get apps side loaded.

Thanks, will be fixed on the next release.

Thanks!

[박훈(Hoon Park)]

Hi secuflag,

Nice work and I appreciate it.

I've tested ATV 9.0 (atv_selfinstall-odroidc4.img.xz) and Android 9.0 (selfinstall-odroidc4.img.xz) and both seem to be working fine.

The only thing is Netflix did something to their app, so I couldn't use a remote to watch movies using the Netflix app on Android TV.

One question for you is how can I gain root access to Android 9.0 file system? From a terminal screen, I couldn't just 'su' to root.

[secuflag]

@박훈(Hoon Park): About root access follow this guide: viewtopic.php?p=248088#p248088

[secuflag]

Someone else could confirm please, the new Play Store (v20.0.45) seems to be working now.

[kyoumaH]

Someone else could confirm please, the new Play Store (v20.0.45) seems to be working now.

Installed ATV 2 days ago, never really had any issues with Play Store navigation even after updating apps. Thanks for the rom!

[박훈(Hoon Park)]

@박훈(Hoon Park): About root access follow this guide: viewtopic.php?p=248088#p248088

Thank you, secuflag!

[Nox997]

Hey, thanks for getting a great Android TV rom out there for the C4! I'm having 2 issues with the build, and I'm wondering if anyone is seeing the same things.

1. I'm using a Plugable USB Bluetooth adapter, and scanning in Android TV is seeing devices (tried a dual shock 4 and another Bluetooth controller), but pairing fails after a few seconds.

2. I've enabled Developer Options via the normal method, but when I try to enter the actual menu, I just get dumped back to the home screen. Obviously this makes it more difficult to get apps side loaded.

Any ideas?

Hi all,

is there any workaround for probem number (2), i.e. how can I sideload without enabling debugging mode OR how can I activate USB debugging without being able to enter the developer options menu?

Thank you very much in advance!

[secuflag]

Hi all, bad bad news here, after 9 years and infinite hours dedicated to compile my Android projects, my mainboard and my power supply broke yesterday :'(
Due to this I can't work on any new release for a while since compile android sources require a powerful workstation.

If you liked my work for C4 and N2 and if you want to help me to buy some new hardware feel free to click the link in my signature.

Many thanks!

[secuflag]

First post updated

Have fun!

[csucsu]

Hi secuflag,

nice work! Is this image usable on another S905X3 board or TV box? What component needs to be change (.dtb etc)?

bets regards,

[secuflag]

Nope, this image is for ODROID-C4 only.

[kyoumaH]

Is there a way to edit remote.conf in the ATV rom? From the logs it seems like only hardkernel's remote is set. Editing remote.tab to add the new remote doesn't work too. Thanks

Code: Select all

odroidc4:/ $  dmesg | grep remote
[    1.008150] <6>[    1.008150@3] meson-remote: Driver init
[    1.008567] <6>[    1.008567@3] meson-remote: remote_probe
[    1.008591] <6>[    1.008591@3] meson-remote ff808040.rc: protocol = 0x1
[    1.008598] <6>[    1.008598@3] meson-remote ff808040.rc: led_blink = 1
[    1.008604] <6>[    1.008604@3] meson-remote ff808040.rc: led_blink_frq  = 100
[    1.008646] <6>[    1.008646@3] meson-remote ff808040.rc: platform_data irq =33
[    1.008711] <6>[    1.008711@3] meson-remote ff808040.rc: custom_number = 1
[    1.008742] <6>[    1.008742@3] meson-remote ff808040.rc: ptable->map_size = 12
[    1.008747] <6>[    1.008747@3] meson-remote ff808040.rc: ptable->custom_name = hardkernel-remote
[    1.008753] <6>[    1.008753@3] meson-remote ff808040.rc: ptable->custom_code = 0x4db2
[    1.008759] <6>[    1.008759@3] meson-remote ff808040.rc: ptable->release_delay = 80
[    1.008768] <6>[    1.008768@3] meson-remote ff808040.rc: default protocol = 0x1 and id = 0
[    1.008774] <6>[    1.008774@3] meson-remote ff808040.rc: reg=0x0, val=0x1f40190
[    1.008778] <6>[    1.008778@3] meson-remote ff808040.rc: reg=0x4, val=0x12c00c8
[    1.008783] <6>[    1.008783@3] meson-remote ff808040.rc: reg=0x8, val=0x960050
[    1.008787] <6>[    1.008787@3] meson-remote ff808040.rc: reg=0xc, val=0x480028
[    1.008792] <6>[    1.008792@3] meson-remote ff808040.rc: reg=0x10, val=0x70fa0013
[    1.008796] <6>[    1.008796@3] meson-remote ff808040.rc: reg=0x18, val=0x8616800
[    1.008800] <6>[    1.008800@3] meson-remote ff808040.rc: reg=0x1c, val=0x9f00
[    1.008805] <6>[    1.008805@3] meson-remote ff808040.rc: reg=0x20, val=0x0
[    1.008809] <6>[    1.008809@3] meson-remote ff808040.rc: reg=0x24, val=0x0
[    1.008814] <6>[    1.008814@3] meson-remote ff808040.rc: reg=0x28, val=0x0

[secuflag]

You should be able to do it using adb;

Code: Select all

$ adb remount
$ adb pull /vendor/etc/remote.cfg
$ adb pull /vendor/etc/remote.tab1

edit files and then push them back

Code: Select all

$ adb push remote.cfg /vendor/etc/remote.cfg
$ adb push remote.tab1 /vendor/etc/remote.tab1

[kyoumaH]

Thanks, I've edited remote.tab2 to match the one I have from another device but it still doesn't work.

C4 original remote.tab2

Code: Select all

custom_name = amlogic-remote-2
custom_code = 0xfe01
release_delay = 80

key_begin
	0x01 2
    0x02 3
    0x03 4
    0x04 5
    0x05 6
    0x06 7
    0x07 8
    0x08 9
    0x09 10
    0x0a 11
    0x1F 466
    0x15 139
    0x16 15
    0x0c 402 
    0x0d 403
    0x0e 115
    0x0f 114
    0x11 102
    0x1c 106
    0x1b 105
    0x19 103
    0x1a 108
    0x1d 28
    0x17 113
    0x49 219
    0x43 158
    0x12 469
    0x14 470
    0x18 471
    0x59 358
    0x5a 166
    0x10 116
    0x42 165
    0x44 163
    0x1e 168
    0x4b 208
    0x58 164
    0x46 130
    0x40 131
    0x38 70
    0x57 464
    0x5b 465
    0x54 398
    0x4c 399
    0x4e 400
    0x55 401
    0x53 237
    0x52 238
    0x39 212
    0x41 213
    0x0b 214
    0x00 216
    0x13 217
key_end

Edited remote.tab2

Code: Select all

custom_name = amlogic-remote-2
custom_code = 0xfe01
release_delay = 80

fn_key_scancode = 0x00
cursor_left_scancode = 0x51
cursor_right_scancode = 0x50
cursor_up_scancode = 0x16
cursor_down_scancode = 0x1a
cursor_ok_scancode = 0x13
key_begin
	0x01 11   #0
        0x4e 2    #1
        0x0d 3    #2
        0x0c 4    #3
        0x4a 5    #4
        0x09 6    #5
        0x08 7    #6
        0x46 8    #7
        0x05 9    #8
        0x04 10   #9
        0x49 63   #F1
        0x48 78   #F2
        0x4d 75   #F3
        0x03 76   #F4
        0x43 77   #F5
        0x45 64   #F6
        0x0f 65   #F7
        0x44 66   #F8
        0x12 67   #F9
        0x4b 68   #F10
        0x26 69   #F11
        0x16 103  #UP
        0x1a 108  #DOWN
        0x51 105  #LEFT
        0x50 106  #RIGHT
        0x13 28   #ENTER
        0x19 158  #BACK
	0x00 127  #SEARCH
        0x4c 125  #MENU
        0x40 116  #POWER
        0x41 113  #MUTE
        0x18 115  #VOLUMEUP
        0x10 114  #VOLUMEDOWN
        0x11 102  #HOME
        0x0a 111  #MUSIC
        0x42 14  #DELETE
        0x47 215  #AT
        0x0e 70  #EXPLORER
        0x59 122 #MEDIAPREVIOUS
        0x58 123 #MEDIANEXT
        0x54 120 #MEDIAFASTFORWARD
        0x52 124  #MEDIAPAUSE
        0x5a 119 #MEDIAPLAYPAUSE
        0x55 121 #MEDIAREWIND
	0x1b 188 #AGING
key_end

[cyl3x]

Together with the android tv rom a wanted to use my ps4 controller, but I cant connect them for no reason (the controller is fine, I can connect stock android from hardkernel) . Is there anything I should know or can try to connect my ds4 to this android tv rom?

[secuflag]

PS4 controller uses bluetooth, should works fine if you use a supported dongle.

[OpenSauce]

C4 android goes to standby whenever TV does.

When turning TV off even for 1 second the c4 then sends "no signal" without wake-up from an infrared remote (even then you have to hold power button for 5 seconds and doesn't consistently turn on (odroid remote))
Was wondering if this could be fixed and/or if you could add an option to keep the device awake/ stop TVs from being able to put it to standby. Android dev "Stay Awake" option does not work because the TV seems to be putting the C4 to standby. Tested on 2 separate TVs (both different models soniq), both put it to standby.

setenv prevent_sleep "1" did not work

Any way to stop this from happening?
Linux build does not have this problem.

[secuflag]

Try to unplug and plug back the HDMI cable, you get "no signal"?