Petitboot, yet another bootloader based on KEXEC

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 2:55 am

@tobetter
Thank you for your help.
1. If I want to install Petitboot must switch to SPI or MMC?
2. Do I have to deposit the Spiboot.img on the CE Edition mSD in boot folder?

tobetter · Post by **tobetter** » Thu Nov 28, 2019 3:04 am

Cosmicbase wrote: ↑
Thu Nov 28, 2019 2:55 am
@tobetter
Thank you for your help.
1. If I want to install Petitboot must switch to SPI or MMC?
2. Do I have to deposit the Spiboot.img on the CE Edition mSD in boot folder?

SPI and copy the firmware file of Petitboot as spiboot.img to boot folder of mSD. Then next power cycle, the current Petitboot in SPI flash memory will read the firmware from mSD and will update itself.

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 3:05 am

OK thanks

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 3:19 am

Does the spiboot.img remain in the boot directory or does it delete automatically after installation?
The SPI switch remains off after installation from SPI?

tobetter · Post by **tobetter** » Thu Nov 28, 2019 3:24 am

Cosmicbase wrote: ↑
Thu Nov 28, 2019 3:19 am
Does the spiboot.img remain in the boot directory or does it delete automatically after installation?
The SPI switch remains off after installation from SPI?

spiboot.img will be removed after the firmware updating is done. If you keep using Petitboot, remain the boot select switch to SPI otherwise Petitboot would not come.

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 3:38 am

tobetter wrote: ↑
Thu Nov 28, 2019 3:24 am

Cosmicbase wrote: ↑
Thu Nov 28, 2019 3:19 am
Does the spiboot.img remain in the boot directory or does it delete automatically after installation?
The SPI switch remains off after installation from SPI?
spiboot.img will be removed after the firmware updating is done. If you keep using Petitboot, remain the boot select switch to SPI otherwise Petitboot would not come.

Thank you, now I have understand.
Petitboot — > SPI Switch, Nomal Boot —> MMC Switch

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 3:52 am

I have one more question!
I do not have an eMMC but a USB 3.0 stick.
USB 3.0 is faster than eMMC as far as I know.
What speaks against using eMMC the USB stick. So Android on the USB stick.

mad_ady · Post by **mad_ady** » Thu Nov 28, 2019 3:59 am

As far as I know android doesn't know how to mount its partitions if they are on usb. It knows only of sd/emmc.

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 4:18 am

Too bad, because I read in the CoreElec forum that Android should work on USB.

tobetter · Post by **tobetter** » Thu Nov 28, 2019 6:06 am

20191127
Let me introduce a new version of Petitboot with a couple of experimental features other than boot management. Personally, I expected to come with a video clip that gives you an idea of how they work, but not this time unfortunately since I am not familiar with such activity and a battery of my camera is discharged while recording.
Please click spiboot-20191127.img to download and copy the file to your uSD card as spiboot.img. Please refer the link for the instruction.
https://wiki.odroid.com/odroid-n2/os_im ... grade_mode

Please enjoy the new version and welcome your feedback.
What's improved:

Supporting U-boot format kernel and ramdisk. Recently, one tried to boot the mainline kernel that built by @elatllat and found another OS uses U-boot format ramdisk. For this issue, I've fixed the bug that U-boot format cannot be booted by Petitboot.

Petitboot can be updated through a network. As you have updated this version, the Petitboot can be updated by copying the file spiboot.img to uSD and power cycle the ODROID-N2. From this version, you can copy and update the firmware in the same manner as well as can update the firmware from Petitboot. In order to check the new version of Petitboot and proceed with the updating, do run command pb-update in the command line.

Some minor bugs are fixed reported by a couple of users.

Known issues:

Some display device does not show anything after Petitboot, this issue frustrating me and it looks like quite depends on OS and display device. The workaround I found for this issue is to change the value of display_autodetect to false from true which is default value of most OS images.

Batocera OS does not boot, I discovered that it has an issue of MMC failure on booting and have not figured out yet. This problem only happens with uSD, not with eMMC or USB storage.

Another known issue I have is that I would not know more issues yet.

Experimental features:
Actually these are the mandatory features what I am expecting to have in SPI boot, these features could help users to manage OS installation.

Debian Netboot installer

I've maintained my own Debian repository, http://ppa.linuxfactory.or.kr, for some time but not many people noticed since I didn't promote. Apart from the packages, mostly Linux kernel, I have uploaded the Debian Netboot installer which is like 50MB only and one can install and setup from scratch rather than flashing the prebuilt OS image. Here is the thread I've started, viewtopic.php?f=55&t=30869

In order to run Debian Netboot installer on Petitboot, just exit to command-line shell and run d-i with Debian OS name, buster or stretch. For example, # d-i buster if you like to install Debian Buster. This command will download the installer image from my repository and get ready to boot from Petitboot. Once downloading is done, get back to Petitboot menu then there will be boot entry for Debian installer. Select it to boot, then you will see the generic Debian installer screen.

Advantage of using Debian Netboot installer that I customized from the genuine installer is that you can install any storage that can be attached to ODROID-N2 and can customize the file system as well as mount entries while installing.

USB Mass Storage mode

This feature is to run ODROID-N2 as a USB Mass Storage such that you can connect ODROID-N2 to your desktop using USB cable, so you can change or update boot.ini or install OS image with your PC without detaching the memory card from ODROID-N2.

Since ODROID-N2 has USB 2.0 OTG port, the performance of the flashing image would be slower than USB card reader. But if you are using USB 2.0 card reader or hesitate to attach and detaching memory card, this feature would work well for you.

This feature is also possible from the command line, run the command ums with the device node of storage. For example, use # ums /dev/mmcblk0 if you like to attach a whole size of eMMC. Your desktop will show you the partitions in the eMMC.

After modifying a file in the memory card or flashing OS image, you must click the detaching button for ODROID-N2 in your PC and run # ums without any argument. The last command will close the USB storage mode and get back to normal storage mode.

If you have flashed OS image using USB Storage mode, you must reboot ODROID-N2. Otherwise, the partition table in the storage won't be affected by Petitboot and Petitboot won't show you the boot entry even though the flashing OS is performed without failure.

Ok, this is what I have today and hope you enjoy using Petitboot on ODROID-N2.

Since this version has an experimental features new approch on ODROID boards, it could be a bit unstable.

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 12:48 pm

What about the remote controls?
If only HK remote control is supported at Petitboot or also Samsung, LIRC, etc.
At Raspberry I use Lirc.
So I save myself remote controls and can operate with a remote control everything.

tobetter · Post by **tobetter** » Thu Nov 28, 2019 1:13 pm

Cosmicbase wrote: ↑
Thu Nov 28, 2019 12:48 pm
What about the remote controls?
If only HK remote control is supported at Petitboot or also Samsung, LIRC, etc.
At Raspberry I use Lirc.
So I save myself remote controls and can operate with a remote control everything.

The current version supports HK stock remote only since Petitboot has everything in a very tiny space (8MB only), not capable to customize the remotes yet.

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 4:22 pm

tobetter wrote: ↑
Thu Nov 28, 2019 1:13 pm

Cosmicbase wrote: ↑
Thu Nov 28, 2019 12:48 pm
What about the remote controls?
If only HK remote control is supported at Petitboot or also Samsung, LIRC, etc.
At Raspberry I use Lirc.
So I save myself remote controls and can operate with a remote control everything.
The current version supports HK stock remote only since Petitboot has everything in a very tiny space (8MB only), not capable to customize the remotes yet.

Ok then I need the remote control from HK to turn on Odroid N2. If Odroid runs with CoreElec then can I also use my Samsung remote via CEC or LIRC? Switching off should also work with Lirc. Only to turn on I have to take HK remote because no Lirc support in Petitboot available.
Did I understand that correctly?

tobetter · Post by **tobetter** » Thu Nov 28, 2019 4:39 pm

Cosmicbase wrote: ↑
Thu Nov 28, 2019 4:22 pm

tobetter wrote: ↑
Thu Nov 28, 2019 1:13 pm

Cosmicbase wrote: ↑
Thu Nov 28, 2019 12:48 pm
What about the remote controls?
If only HK remote control is supported at Petitboot or also Samsung, LIRC, etc.
At Raspberry I use Lirc.
So I save myself remote controls and can operate with a remote control everything.
The current version supports HK stock remote only since Petitboot has everything in a very tiny space (8MB only), not capable to customize the remotes yet.
Ok then I need the remote control from HK to turn on Odroid N2. If Odroid runs with CoreElec then can I also use my Samsung remote via CEC or LIRC? Switching off should also work with Lirc. Only to turn on I have to take HK remote because no Lirc support in Petitboot available.
Did I understand that correctly?

It's a bit complicated.
CoreELEC can run with Samsung remote or LIRC since it's CoreELEC feature. Even you could use HK stock remote with CE and you can turn off with everything. The problem is that U-boot for CE and Android from HK are different and this makes an awkward situation that ODROID-N2 cannot resume once it suspends from CE. This is because the CE team changes the method of IR suspend and I have not mixed them with HK code for some reason. But CEC wakes up work, I have not tested it yet. I think this question could be answered by CE users with the exact situation since there are many users who run Android + CE combo with Petitboot.
https://discourse.coreelec.org/

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 4:48 pm

tobetter wrote: ↑
Thu Nov 28, 2019 4:39 pm

Cosmicbase wrote: ↑
Thu Nov 28, 2019 4:22 pm

tobetter wrote: ↑
Thu Nov 28, 2019 1:13 pm

Cosmicbase wrote: ↑
Thu Nov 28, 2019 12:48 pm
What about the remote controls?
If only HK remote control is supported at Petitboot or also Samsung, LIRC, etc.
At Raspberry I use Lirc.
So I save myself remote controls and can operate with a remote control everything.
The current version supports HK stock remote only since Petitboot has everything in a very tiny space (8MB only), not capable to customize the remotes yet.
Ok then I need the remote control from HK to turn on Odroid N2. If Odroid runs with CoreElec then can I also use my Samsung remote via CEC or LIRC? Switching off should also work with Lirc. Only to turn on I have to take HK remote because no Lirc support in Petitboot available.
Did I understand that correctly?
It's a bit complicated.
CoreELEC can run with Samsung remote or LIRC since it's CoreELEC feature. Even you could use HK stock remote with CE and you can turn off with everything. The problem is that U-boot for CE and Android from HK are different and this makes an awkward situation that ODROID-N2 cannot resume once it suspends from CE. This is because the CE team changes the method of IR suspend and I have not mixed them with HK code for some reason. But CEC wakes up work, I have not tested it yet. I think this question could be answered by CE users with the exact situation since there are many users who run Android + CE combo with Petitboot.
https://discourse.coreelec.org/

So once you have the HK remote control is the best to handle everything.
1. I can turn on the Odroid N2.
2. I can select in Petitboot whether Android or CE should start.
3. I can operate the Odroid N2 with the HK remote control both CE and Android
4. I can turn Android as well as CE off.
5. Does CEC play a major role in operating Android and CE?
6. CEC WakeUP is well great, but i can`t switch between Android and CE on starting petitboot without HK remote control. My Samsung IR Mouse is not Usefull without Lirc. I have to buy a HK control.
7. I only use lirc for the power button to switch on/off. for the rest i use cec. at the moment i use remotePi on my Raspi (remotePi is a IR modul for Raspi).

These points should work.

Cosmicbase · Post by **Cosmicbase** » Thu Nov 28, 2019 8:24 pm

@tobetter

1. Is there an Airmouse as well as Beelink GT-King?
This Airmouse also has voice input, which I find very convenient.
Voice command is very useful for VOD (Netflix,Co)
3. Does the speech input work on CoreElec or Android only?
4. Is an Airmouse also available from HK or in planning?

tobetter · Post by **tobetter** » Thu Nov 28, 2019 9:52 pm

Cosmicbase wrote:@tobetter

1. Is there an Airmouse as well as Beelink GT-King?
This Airmouse also has voice input, which I find very convenient.
Voice command is very useful for VOD (Netflix,Co)
3. Does the speech input work on CoreElec or Android only?
4. Is an Airmouse also available from HK or in planning?

Voice command is not officially supported yet, but we've ordered a sample early this week and will test if it can work or not.

One small request is please do let here more discuss about Petitboot only and create your own thread about your doubts about ODROID-N2. Myself or someone else will keep helping you anyway.

"Tapatalk wishes you to have fun with ODROID"

odroidn2user · Post by **odroidn2user** » Sat Nov 30, 2019 2:05 am

tobetter wrote: ↑
Thu Nov 28, 2019 6:06 am
20191127

Still not actually booting Manjaro ARM on my Odroid N2 as far as I can tell.
Also: no support for the MS Natural Ergonomic keyboard. And: screen on my LG M2352 stays black, with true and with false on the auto detect.
But: the Petitboot menu on my SyncMaster 203B 1400x1050 is now actually visible en legible (showing in a wrong resolution, so the image is a bit squished).

tobetter · Post by **tobetter** » Sat Nov 30, 2019 2:40 am

odroidn2user wrote: ↑
Sat Nov 30, 2019 2:05 am

tobetter wrote: ↑
Thu Nov 28, 2019 6:06 am
20191127
Still not actually booting Manjaro ARM on my Odroid N2 as far as I can tell.
Also: no support for the MS Natural Ergonomic keyboard. And: screen on my LG M2352 stays black, with true and with false on the auto detect.
But: the Petitboot menu on my SyncMaster 203B 1400x1050 is now actually visible en legible (showing in a wrong resolution, so the image is a bit squished).

When I had tested Manjaro before the release, even it didn't boot from a memory card without the Petitboot. Then I've not looked into it yet, will do later.
Well...I do not have MS Natural Ergonomic Keyboard. But if it's fully compatible with USB HID device, it should work. If it requires its own driver in linux, please let me know if you know.
For your display, in the shell of Petitboot please share the output of the command # cat /proc/cmdline.

felixob · Post by **felixob** » Wed Dec 04, 2019 2:42 am

Hello, I'm new to this forum. I own a N2 and have been running coreelec on mSD for months (I have no eMMC). Now I wanted to try android, so I started playing with petitboot and have a problem. I'll try to explain what I've done step-by-step:

1. Installed/updated petitboot without problems. Changing de switch to SPI, it starts without any OS in mSD/USB. ok.
2. Using the mSD with coreelec and the switch in SPI position, it starts ok. coreelec is recognized and starts. ok.
3. With the same mSD card, using a USB 3.0 adapter, it's also ok.
4. Install android in another mSD card. With the switch in eMMC/SD postion, the system starts and android works. ok.
5. Try both OSs at the same time, android in mSD and coreelec in USB, with the switch in SPI position. petitboot starts, both systems are recognized. ok.
6. Select start from coreelec. System starts. ok.
7. Select start from android. System tries to start but ends blocked.

I have installed the latest versions available of all OSs. I tried may times with android, with different releases (android, ATV, lineage) with similar results. The systems gets always stuck in the HK logo or a black screen. I know there are other users with similar problems (for example, viewtopic.php?f=182&t=33873&start=350#p271136). I searched in the forum but I can't find a solution (if exists).

Anyway, thanks a lot for your work.

tobetter · Post by **tobetter** » Wed Dec 04, 2019 3:03 am

felixob wrote: ↑
Wed Dec 04, 2019 2:42 am
Hello, I'm new to this forum. I own a N2 and have been running coreelec on mSD for months (I have no eMMC). Now I wanted to try android, so I started playing with petitboot and have a problem. I'll try to explain what I've done step-by-step:

1. Installed/updated petitboot without problems. Changing de switch to SPI, it starts without any OS in mSD/USB. ok.
2. Using the mSD with coreelec and the switch in SPI position, it starts ok. coreelec is recognized and starts. ok.
3. With the same mSD card, using a USB 3.0 adapter, it's also ok.
4. Install android in another mSD card. With the switch in eMMC/SD postion, the system starts and android works. ok.
5. Try both OSs at the same time, android in mSD and coreelec in USB, with the switch in SPI position. petitboot starts, both systems are recognized. ok.
6. Select start from coreelec. System starts. ok.
7. Select start from android. System tries to start but ends blocked.

I have installed the latest versions available of all OSs. I tried may times with android, with different releases (android, ATV, lineage) with similar results. The systems gets always stuck in the HK logo or a black screen. I know there are other users with similar problems (for example, viewtopic.php?f=182&t=33873&start=350#p271136). I searched in the forum but I can't find a solution (if exists).

Anyway, thanks a lot for your work.

Does your Android in uSD work when CE in USB stick is not attached through Petitboot?
What's the vendor of uSD for Android?
Do you have a USB-to-Serial debugging board?

felixob · Post by **felixob** » Wed Dec 04, 2019 3:35 am

tobetter wrote: ↑
Wed Dec 04, 2019 3:03 am
Does your Android in uSD work when CE in USB stick is not attached through Petitboot?
What's the vendor of uSD for Android?
Do you have a USB-to-Serial debugging board?

Well, that's funny. I'd never tried to start petitboot with ONLY android, as you say (my error). Now I tried and it has worked !!!
Even more funny: after that, I plugged again the USB with CE and all works ok. Now I can start both OSs from petitboot without any problems. I tried 4 or 5 times and all worked ok.
My mSDs are Samsung EVO and SanDisk Ultra (I think I tried both with different android releases). And sorry, I don't have a debugging board.
Thanks a lot again for your answer. It's been magic. And sorry for the inconvenience.
Could you please give me a little explanation of this issue?

tobetter · Post by **tobetter** » Wed Dec 04, 2019 12:16 pm

felixob wrote: ↑
Wed Dec 04, 2019 3:35 am

tobetter wrote: ↑
Wed Dec 04, 2019 3:03 am
Does your Android in uSD work when CE in USB stick is not attached through Petitboot?
What's the vendor of uSD for Android?
Do you have a USB-to-Serial debugging board?
Well, that's funny. I'd never tried to start petitboot with ONLY android, as you say (my error). Now I tried and it has worked !!!
Even more funny: after that, I plugged again the USB with CE and all works ok. Now I can start both OSs from petitboot without any problems. I tried 4 or 5 times and all worked ok.
My mSDs are Samsung EVO and SanDisk Ultra (I think I tried both with different android releases). And sorry, I don't have a debugging board.
Thanks a lot again for your answer. It's been magic. And sorry for the inconvenience.
Could you please give me a little explanation of this issue?

No worries, nothing inconvenient.
I could explain once I try out the same as what you did.
By the time, please do blame me whatever you meet a mysterious thing on Petitboot.

Cosmicbase · Post by **Cosmicbase** » Thu Dec 05, 2019 8:45 pm

felixob wrote: ↑
Wed Dec 04, 2019 3:35 am

tobetter wrote: ↑
Wed Dec 04, 2019 3:03 am
Does your Android in uSD work when CE in USB stick is not attached through Petitboot?
What's the vendor of uSD for Android?
Do you have a USB-to-Serial debugging board?
Well, that's funny. I'd never tried to start petitboot with ONLY android, as you say (my error). Now I tried and it has worked !!!
Even more funny: after that, I plugged again the USB with CE and all works ok. Now I can start both OSs from petitboot without any problems. I tried 4 or 5 times and all worked ok.
My mSDs are Samsung EVO and SanDisk Ultra (I think I tried both with different android releases). And sorry, I don't have a debugging board.
Thanks a lot again for your answer. It's been magic. And sorry for the inconvenience.
Could you please give me a little explanation of this issue?

So does the petitboot work with Android mSD and USB CE together?
Can I then choose whether to start Android via mSD or CE via USB?

loznic89 · Post by **loznic89** » Thu Dec 05, 2019 11:41 pm

https://jungle-team.com/odroid-n2-insta ... enamiento/

https://jungle-team.com/instalar-petitb ... odroid-n2/

tutorials in spanish language about updating petitboot and install dual OS in sdcard/usb

felixob · Post by **felixob** » Fri Dec 06, 2019 2:21 am

Cosmicbase wrote: ↑
Thu Dec 05, 2019 8:45 pm

felixob wrote: ↑
Wed Dec 04, 2019 3:35 am

tobetter wrote: ↑
Wed Dec 04, 2019 3:03 am
Does your Android in uSD work when CE in USB stick is not attached through Petitboot?
What's the vendor of uSD for Android?
Do you have a USB-to-Serial debugging board?
Well, that's funny. I'd never tried to start petitboot with ONLY android, as you say (my error). Now I tried and it has worked !!!
Even more funny: after that, I plugged again the USB with CE and all works ok. Now I can start both OSs from petitboot without any problems. I tried 4 or 5 times and all worked ok.
My mSDs are Samsung EVO and SanDisk Ultra (I think I tried both with different android releases). And sorry, I don't have a debugging board.
Thanks a lot again for your answer. It's been magic. And sorry for the inconvenience.
Could you please give me a little explanation of this issue?
So does the petitboot work with Android mSD and USB CE together?
Can I then choose whether to start Android via mSD or CE via USB?

Yes, in my case all is working without any issues now. I have CE in USB and lineage ATV in uSD, both are recognized by petitboot and I can select any of them to boot.
I don't know why, but I had to start the system ONE TIME with ONLY android plugged. After that, all works.

Cosmicbase · Post by **Cosmicbase** » Sat Dec 07, 2019 5:31 am

OK thanks.
Then I do not need to buy an extra eMMC card.
USB 3.0 stick and uSD card I have.

Cosmicbase · Post by **Cosmicbase** » Sat Dec 07, 2019 5:54 am

felixob wrote: ↑
Fri Dec 06, 2019 2:21 am

Cosmicbase wrote: ↑
Thu Dec 05, 2019 8:45 pm

felixob wrote: ↑
Wed Dec 04, 2019 3:35 am

tobetter wrote: ↑
Wed Dec 04, 2019 3:03 am
Does your Android in uSD work when CE in USB stick is not attached through Petitboot?
What's the vendor of uSD for Android?
Do you have a USB-to-Serial debugging board?
Well, that's funny. I'd never tried to start petitboot with ONLY android, as you say (my error). Now I tried and it has worked !!!
Even more funny: after that, I plugged again the USB with CE and all works ok. Now I can start both OSs from petitboot without any problems. I tried 4 or 5 times and all worked ok.
My mSDs are Samsung EVO and SanDisk Ultra (I think I tried both with different android releases). And sorry, I don't have a debugging board.
Thanks a lot again for your answer. It's been magic. And sorry for the inconvenience.
Could you please give me a little explanation of this issue?
So does the petitboot work with Android mSD and USB CE together?
Can I then choose whether to start Android via mSD or CE via USB?
Yes, in my case all is working without any issues now. I have CE in USB and lineage ATV in uSD, both are recognized by petitboot and I can select any of them to boot.
I don't know why, but I had to start the system ONE TIME with ONLY android plugged. After that, all works.

Can I also take Android 9 instead of LineAgeATV
viewtopic.php?f=178&t=35463 ?

tobetter · Post by **tobetter** » Sat Dec 07, 2019 11:41 am

Cosmicbase wrote: ↑
Sat Dec 07, 2019 5:54 am

felixob wrote: ↑
Fri Dec 06, 2019 2:21 am

Cosmicbase wrote: ↑
Thu Dec 05, 2019 8:45 pm

felixob wrote: ↑
Wed Dec 04, 2019 3:35 am

tobetter wrote: ↑
Wed Dec 04, 2019 3:03 am
Does your Android in uSD work when CE in USB stick is not attached through Petitboot?
What's the vendor of uSD for Android?
Do you have a USB-to-Serial debugging board?
Well, that's funny. I'd never tried to start petitboot with ONLY android, as you say (my error). Now I tried and it has worked !!!
Even more funny: after that, I plugged again the USB with CE and all works ok. Now I can start both OSs from petitboot without any problems. I tried 4 or 5 times and all worked ok.
My mSDs are Samsung EVO and SanDisk Ultra (I think I tried both with different android releases). And sorry, I don't have a debugging board.
Thanks a lot again for your answer. It's been magic. And sorry for the inconvenience.
Could you please give me a little explanation of this issue?
So does the petitboot work with Android mSD and USB CE together?
Can I then choose whether to start Android via mSD or CE via USB?
Yes, in my case all is working without any issues now. I have CE in USB and lineage ATV in uSD, both are recognized by petitboot and I can select any of them to boot.
I don't know why, but I had to start the system ONE TIME with ONLY android plugged. After that, all works.
Can I also take Android 9 instead of LineAgeATV
viewtopic.php?f=178&t=35463 ?

It must be working.

Cosmicbase · Post by **Cosmicbase** » Sun Dec 08, 2019 5:14 pm

1.What is better for Petitboot AOSP Android Pie or LineAgeOS 16.0 or LineAgeOS 16.0 ATV?
2. What is more stable?
3. Which is the latest and the best support?
4. Who supports Rii MX9 Wireless Airmouse (https://www.google.com/search?rlz=1C1GC ... 20&bih=932)

Thanks for help

felixob · Post by **felixob** » Sun Dec 08, 2019 8:11 pm

Cosmicbase wrote: ↑
Sun Dec 08, 2019 5:14 pm
1.What is better for Petitboot AOSP Android Pie or LineAgeOS 16.0 or LineAgeOS 16.0 ATV?
2. What is more stable?
3. Which is the latest and the best support?
4. Who supports Rii MX9 Wireless Airmouse (https://www.google.com/search?rlz=1C1GC ... 20&bih=932)

Thanks for help

I couldn't tell you what android is better. Now I have installed lineage ATV, but I don't use it a lot. Most of the time, I use CoreElec.
Usually all RF airmouses work. I have tested two of them without any issue.

Cosmicbase · Post by **Cosmicbase** » Sun Dec 08, 2019 8:21 pm

ok Thanks

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 2:13 am

Sorry if I'm intruding guys, but I can't go on. I installed the latest Petitboot version (dev 20191111), I have two operating systems installed, one is coreelec on emmc and usb while on sd I installed android. When petitboot leaves me it detects both boot tabs, but while if I choose to start android it works when I choose coreelec instead the screen remains black, yet the blue light turns on as if it is loading the system but I don't see anything. Something wrong. Thanks.

tobetter · Post by **tobetter** » Mon Dec 09, 2019 2:44 am

marcavatar wrote: ↑
Mon Dec 09, 2019 2:13 am
Sorry if I'm intruding guys, but I can't go on. I installed the latest Petitboot version (dev 20191111), I have two operating systems installed, one is coreelec on emmc and usb while on sd I installed android. When petitboot leaves me it detects both boot tabs, but while if I choose to start android it works when I choose coreelec instead the screen remains black, yet the blue light turns on as if it is loading the system but I don't see anything. Something wrong. Thanks.

Can you please update with the latest Petitboot (dev.20191127)?
https://wiki.odroid.com/odroid-n2/os_im ... ev20191127

What's the version of CoreELEC or image file name of it?

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 2:58 am

thanks for the reply, then coreelec is the latest version 9.2.1, I loaded the boot on emmc while the rest having several movies on usb

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 2:59 am

In practice it sees me the flash of the boot but the usb detects it as a disk and not as usb

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 4:58 am

I discovered one thing, basically using tigervnc I can see coreelec on pc and use it from there, but on the TV screen where the nroid is connected the screen is black. Do I have to change some parameters?

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 5:54 am

Practically to visualize the screen of Coreelec I have to move with the remote control on a hdmi port different from the one where the odroid is connected to then return to the default one and at that point the screen appears. Such a thing had never happened to me before. Has it happened to you?

tobetter · Post by **tobetter** » Mon Dec 09, 2019 8:54 am

marcavatar wrote:Practically to visualize the screen of Coreelec I have to move with the remote control on a hdmi port different from the one where the odroid is connected to then return to the default one and at that point the screen appears. Such a thing had never happened to me before. Has it happened to you?

Is this happened after you update the Petitboot or CoreELEC 9.2.1?

"Tapatalk wishes you to have fun with ODROID"

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 8:56 pm

CoreElec I had it for quite some time it was updated about ten days ago, instead petitboot I installed it yesterday along with the android system, coreelec on emmc and usb while android on sd card where I then inserted petitboot.

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 8:57 pm

I updated Petitboot after installing android before I had the 20191111 version now I have the 20192711 version

marcavatar · Post by **marcavatar** » Mon Dec 09, 2019 8:59 pm

In practice, to view coreelec I have to change the source on the remote control and then go back to the one where the hdmi is inserted and only then can I see everything.

rooted · Post by **rooted** » Mon Dec 09, 2019 9:24 pm

marcavatar wrote:In practice, to view coreelec I have to change the source on the remote control and then go back to the one where the hdmi is inserted and only then can I see everything.

I think this is the same issue expressed in this thread:

viewtopic.php?p=274476

Not exactly a CoreELEC issue as much as a general display issue with HDMI on the N2. I think this will be resolved now it's known to happen.

alpe · Post by **alpe** » Mon Dec 09, 2019 10:39 pm

tobetter wrote: ↑
Thu Nov 28, 2019 6:06 am
Known issues:
Some display device does not show anything after Petitboot, this issue frustrating me and it looks like quite depends on OS and display device. The workaround I found for this issue is to change the value of display_autodetect to false from true which is default value of most OS images.

Changing to false didn't work for me.
Look: viewtopic.php?p=274476

marcavatar · Post by **marcavatar** » Tue Dec 10, 2019 9:20 pm

Hi guys, I have an update
I tried to pass the hdmi signal on my yamaha rx-v765 amplifier equipped with a hdmi port and it works, the images of the operating systems are seen on the screen and load without any problems with my amazement with any sequence.

minoccio · Post by **minoccio** » Sat Dec 14, 2019 8:32 pm

I have a full working petitboot config with Android 32 bit on uSD (KODAK 64gb) and Coreelec 9.2.1 on eMMC. Today I tried to install Lineage 64 bit on a Samsung 64gb uSD, and when I select uSD with android, sistem stuck on Hardkernel logo and blue led steady light. If I select Coreelec system boot. The uSD with Android Lineage 64 bit works when I boot without emmc (switch on emmc)

felixob · Post by **felixob** » Sun Dec 15, 2019 4:49 pm

minoccio wrote: ↑
Sat Dec 14, 2019 8:32 pm
I have a full working petitboot config with Android 32 bit on uSD (KODAK 64gb) and Coreelec 9.2.1 on eMMC. Today I tried to install Lineage 64 bit on a Samsung 64gb uSD, and when I select uSD with android, sistem stuck on Hardkernel logo and blue led steady light. If I select Coreelec system boot. The uSD with Android Lineage 64 bit works when I boot without emmc (switch on emmc)

Maybe you could try to boot the system with petitboot and ONLY lineage installed (remove the eMMC with CE). It that works, then plug the eMMC with CE and try again.
That worked for me (a few posts above).

minoccio · Post by **minoccio** » Mon Dec 16, 2019 3:19 am

It didn't work for me...

felixob · Post by **felixob** » Mon Dec 16, 2019 4:51 am

My android is lineage ATV, from this link:
viewtopic.php?f=178&t=35484

AviatorBimmer · Post by **AviatorBimmer** » Mon Dec 23, 2019 5:05 am

I have an Odroid N2 and finished upgrading the Petitboot to 20191127.

My N2 has a 32GB eMMC installed.

I took a micro usb cable and connected it to the micro usb connector on my N2 and the USB connector to my PC desktop, turned on the N2 but my PC is not recognizing the N2.

How do I enable USB Mass Storage Mode on the N2, so I can access the eMMC card directly from my PC and flash/write CoreElec on the eMMC?

Thanks in advance!