Sailfish OS on ONDA V820W V3 and other Intel SoC-based tablets

[TheKit]

I got pretty much inspired by https://jolla.comes.today/jolla-tablet-on-taobao-china/ article and firmware from http://talk.maemo.org/showthread.php?t=96474. In a nutshell, official Jolla Tablet is a device based around Intel Atom Z3735F SoC (Bay Trail) and can work both with Sailfish OS and Android (by the way, Android device tree it's based on is called "anzhen4_mrd8_w").

There have been a lot of cheap Chinese tablet using the same SoC, and usually they come with Android/Windows dualboot. So what's preventing us from running Sailfish OS on them? Android firmware can often be easily ported between such devices, but kernel is device-specific, so custom ROM makers just use the stock kernel from their device unmodified.

For Sailfish OS, we can't, since systemd requires some kernel options which are most of time turned off in Android kernels. Enabling them and recompiling kernel would be easy if Chinese manufacturers didn't violate GPL and actually provided kernel sources, but that's not the case. Thankfully, since most of hardware is similar, it's possible to base custom kernel on other device source.

I have Sailfish OS running on Onda V820w tablet. It's not perfect yet, but the hardware itself (touchscreen, audio, Wi-Fi, Bluetooth, front and back cameras) works. Many thanks to Stskeeps for providing modules folders which were missing from Jolla Tablet kernel sources. The biggest problem was getting kernel working with camera sensors. Even though the needed drivers are present, PMIC regs and GPIO pin meanings turned out to be different. Just a few values to change, but it was very troublesome to debug and I had to disassemble Onda stock Android kernel to understand what's wrong.

Below is a guide to installing Sailfish OS on Onda V820w (tested with V3, see serial number to understand what revision is yours if you happen to have it). Hope community will be interested in running Sailfish OS on other similar devices and we can have more supported. I'm happy to help with what I can either here or at #sailfishos-porters on IRC.


Onda V820w (V3) manual install guide
Make sure you have USB keyboard and OTG cable, it's required for navigating in UEFI setup.

1. Make ext4 partition at least 2 GiB large on your microSD card. GParted is your friend in this. It's also possible to use internal NAND, but this would require booting Linux LiveCD on tablet for partitioning, using microSD is easier and safer for testing.

2. You can either download Jolla Tablet firmware yourself and extract root/home partition. On Jolla Tablet LVM is used with separate partitions for root, /home and /fimage (recovery images). I didn't use this structure since it complicates testing and amount of available space on tablet is pretty low, and instead moved /home contents on root partition. /fimage is not needed since we don't have recovery images anyway. Then overwrite the contents of root partition with the contents of "root" folder from https://github.com/NotKit/sailfishos-onda-v820w-overlay.

Or you can use the rootfs tarball I prepared (Sailfish OS updated to the latest version): https://mega.nz/#!cBZ2XZ6L!P3EIFFQzelAxK7203LIxY6jqbDHSp6lNcJnyOvj sArA

3. Now you need to adjust the contents of grub.cfg in /boot.
root= should to point to the right partition, /dev/mmcblk1p2 by default for second partition on microSD card.
Since the tablet can't boot from SD card, we need to copy bzImage, grubia32.efi and grub.cfg from /boot to the root of internal NAND ESP partition. If you have root access in Android, you can mount it like this:
su
mkdir /data/local/esp
mount -t vfat /dev/mmcblk0p1 /data/local/esp

4. Connect USB keyboard and reboot the tablet, holding Esc key. It should go to the boot menu. Select "Boot From File" option and chose ESP partition in the list, then launch grubia32.efi.

The first option in GRUB should normally boot Sailfish OS. First boot is going to take around a minute, but If you have black screen for too long, try pressing power button.

The second (init-debug) enables USB networking and telnet daemon as specified in 9.2 of HADK porting guide. It halts booting until you connect via telnet and tell it to continue, so don't expect anything but black screen until then.

Here are some photos how it looks like if you get it running: http://imgur.com/a/2CIVo


Update: automatic installer (all data is going to be erased!) image for ONDA V820W V3: https://mega.nz/#!8FZRiBwB!FBBD8CUMaBMkKcyiUDlw_sKfCjNZOQp713VqT-FoAhM. Unpack it to the root of FAT32 formatted USB drive and boot tablet from USB drive.

[nodevel]

Hi, sorry for replying so late, but this really caught my attention as it could be a cheaper alternative to the Jolla Tablet. First, I want to thank you for the detailed tutorial and for the effort.

Would you (or anyone else with this tablet) please be willing to share any experience with using it for a few weeks?

What about the battery life? How much power does it draw when idle?
Does the miniHDMI-out work?

And the final question - since the port is based on the Jolla Tablet files (if I understand it correctly) and it uses the same kernel version, do the proprietary parts of SailfishOS work as well? Namely Alien Dalvik, Jolla Store and MS Exchange (never used it, but I'm curious).

Thanks.

[deutch1976]

Hi there
Also interested for my
Toshiba Encore WT8-A-103

Specifications

Toshiba Encore WT8-A-103Notebook: Toshiba Encore WT8-A-103 (Encore Series)
Processor: Intel Atom Z3740
Graphics Adapter: Intel HD Graphics (Bay Trail)
Would be great it someone could make a port for it

[TheKit]

Hi, sorry for replying so late, but this really caught my attention as it could be a cheaper alternative to the Jolla Tablet. First, I want to thank you for the detailed tutorial and for the effort.

Would you (or anyone else with this tablet) please be willing to share any experience with using it for a few weeks?

What about the battery life? How much power does it draw when idle?
Does the miniHDMI-out work?

And the final question - since the port is based on the Jolla Tablet files (if I understand it correctly) and it uses the same kernel version, do the proprietary parts of SailfishOS work as well? Namely Alien Dalvik, Jolla Store and MS Exchange (never used it, but I'm curious).

Thanks.
Unfortunately, I was more interested in getting SailfishOS running on it than actually using the device, so can't really share much user experience. Battery should be around 3 hours for general use. miniHDMI is untested, since I don't have a display to plug it in, but it probably won't work, since Sailfish OS doesn't support more than one screen so far and they purposefully shipped Jolla Tablet without HDMI port.

As for the device itself, build quality/official OS (Windows/Android I mean) support/etc is not to be compared with more expensive devices, but it still does a lot for the price in terms of hardware itself.

And for the last question, yes, but it probably goes against the rules.


Hi there
Also interested for my Toshiba Encore WT8-A-103

Since your device doesn't have official Android firmware, libhybris can't be used, but pure Linux adaptation will be probably much more generic. You can try running latest build of Remix OS (http://www.jide.com/remixos-for-pc#downloadNow) and Android-x86 itself (they've integrated many kernel patches for Bay Trail) or general Linux distro to see what in terms of hardware support is likely to work and what's not.

[MJ m]

Hi there
Also interested for my
Toshiba Encore WT8-A-103

Specifications

Toshiba Encore WT8-A-103Notebook: Toshiba Encore WT8-A-103 (Encore Series)
Processor: Intel Atom Z3740
Graphics Adapter: Intel HD Graphics (Bay Trail)
Would be great it someone could make a port for it

+1 for Encore port. Btw, have you tried getting your encore to dnx/fastboot mode? mine just flashes the dnx mode screen and continues booting, whereas on my jolla tablet dnx mode works correctly?:confused:

[explit]

Any chances for Nokia N1? Have an TW-Version (Android 5.0.2) with unlocked boot loader.
But i can't find kernel and android sources for this Tablet.

[smatkovi]

+1 for Encore port. Btw, have you tried getting your encore to dnx/fastboot mode? mine just flashes the dnx mode screen and continues booting, whereas on my jolla tablet dnx mode works correctly?:confused:

i bricked my tablet by flashing sfos with fastboot. any ideas how to unbrick? i cannot even flash original os

[explit]

i bricked my tablet by flashing sfos with fastboot. any ideas how to unbrick? i cannot even flash original os

which one?
I think, now you need to put your Tablet into Flash mode and flash it with Intel Phone Flash Tool or Intel Plattform flash tool

[smatkovi]

which one?
I think, now you need to put your Tablet into Flash mode and flash it with Intel Phone Flash Tool or Intel Plattform flash tool

the onda v820w, i used both tools, but it gives me an error like flashing ifwi failed - sn. i tried sfos, android 5 for this tablet and the factory image for android, how i understood

[smatkovi]

now i maybe try booting a life cd and putting sfos to the internal nand. the question is how i get grub.cfg bzimage and grubia32.efi. but maybe ihave to install a Linux to have it

[smatkovi]

hopefully they are in the rootfs tarball and work for the internal nand also

[nodevel]

the onda v820w, i used both tools, but it gives me an error like flashing ifwi failed - sn. i tried sfos, android 5 for this tablet and the factory image for android, how i understood

How did you try flashing SailfishOS on that Onda thing?

Based on the first post in this thread (and my research), the only way to run SailfishOS on it is to boot it off a microSD card.

[smatkovi]

How did you try flashing SailfishOS on that Onda thing?

Based on the first post in this thread (and my research), the only way to run SailfishOS on it is to boot it off a microSD card.

like it was a jolla tablet from taobao, only it isn't. how are the internal partitions called ?

[TheKit]

Any chances for Nokia N1? Have an TW-Version (Android 5.0.2) with unlocked boot loader.
But i can't find kernel and android sources for this Tablet.
I wonder if Nokia will reply to kernel sources request. I know it's not manufactured by them, but still... Otherwise your best bet is to look for devices with the same SoC (Intel Atom Z3580 - Moorefield). For example, I found Dell Venue 8 7840 - http://opensource.dell.com/releases/Venue_8_7840_Moorefield/. Core hardware should work, but no idea what else will and what not. You can contact me in IRC if you want to do some tinkering.

the onda v820w, i used both tools, but it gives me an error like flashing ifwi failed - sn. i tried sfos, android 5 for this tablet and the factory image for android, how i understood
Please confirm if it's Onda V820w or Onda V820W CH and what revision (look for serial number at the back side). And yes, you can't flash original Jolla Tablet image via fastboot. Hardware is still a little different.

How did you try flashing SailfishOS on that Onda thing?

Based on the first post in this thread (and my research), the only way to run SailfishOS on it is to boot it off a microSD card.
Booting off microSD isn't a requirement, you can install it into NAND like a general Linux distro (except partitioning/copying files needs to be done manually), it's just more safe to start from. I have it in NAND on mine.

[smatkovi]

I wonder if Nokia will reply to kernel sources request. I know it's not manufactured by them, but still... Otherwise your best bet is to look for devices with the same SoC (Intel Atom Z3580 - Moorefield). For example, I found Dell Venue 8 7840 - http://opensource.dell.com/releases/Venue_8_7840_Moorefield/. Core hardware should work, but no idea what else will and what not. You can contact me in IRC if you want to do some tinkering.


Please confirm if it's Onda V820w or Onda V820W CH and what revision (look for serial number at the back side). And yes, you can't flash original Jolla Tablet image via fastboot. Hardware is still a little different.


Booting off microSD isn't a requirement, you can install it into NAND like a general Linux distro (except partitioning/copying files needs to be done manually), it's just more safe to start from. I have it in NAND on mine.
how did you do it?^^

[explit]

I wonder if Nokia will reply to kernel sources request. I know it's not manufactured by them, but still... Otherwise your best bet is to look for devices with the same SoC (Intel Atom Z3580 - Moorefield). For example, I found Dell Venue 8 7840 - http://opensource.dell.com/releases/Venue_8_7840_Moorefield/. Core hardware should work, but no idea what else will and what not. You can contact me in IRC if you want to do some tinkering.


Please confirm if it's Onda V820w or Onda V820W CH and what revision (look for serial number at the back side). And yes, you can't flash original Jolla Tablet image via fastboot. Hardware is still a little different.


Booting off microSD isn't a requirement, you can install it into NAND like a general Linux distro (except partitioning/copying files needs to be done manually), it's just more safe to start from. I have it in NAND on mine.

I asked alredy Foxconn for Android Sources and Kernel but got of course no answer...

I have an second Nokia N1 (Chinese Modell), which i bought for spear parts....
I can try to flash Sailfish on it, or you think it wouldn't be so easy?

[smatkovi]

I wonder if Nokia will reply to kernel sources request. I know it's not manufactured by them, but still... Otherwise your best bet is to look for devices with the same SoC (Intel Atom Z3580 - Moorefield). For example, I found Dell Venue 8 7840 - http://opensource.dell.com/releases/Venue_8_7840_Moorefield/. Core hardware should work, but no idea what else will and what not. You can contact me in IRC if you want to do some tinkering.


Please confirm if it's Onda V820w or Onda V820W CH and what revision (look for serial number at the back side). And yes, you can't flash original Jolla Tablet image via fastboot. Hardware is still a little different.


Booting off microSD isn't a requirement, you can install it into NAND like a general Linux distro (except partitioning/copying files needs to be done manually), it's just more safe to start from. I have it in NAND on mine.

sn is P820DBG2V5A02794, what does that mean?^^

[smatkovi]

How did you try flashing SailfishOS on that Onda thing?

Based on the first post in this thread (and my research), the only way to run SailfishOS on it is to boot it off a microSD card.

have you also got a 32bit efi bios?

[smatkovi]

summary of what i did so far: i installed debian on the tablet but it seemed like while boot the display gets turned off, even with ctrl + alt + f1 i didn't see anything, anyway i managed to copy the 3 files to the bootpartition from a usb-stick, from which i booted the debian live cd, then my cable got a loose contact so i decided to copy the tarball to the sdcard and start the copyingprocess, but unfortunately i couldn't make contact with the cable, so i couldn't use the keyboard. next i will buy a new usb-cable and copy the files to the datapartition. then hopefully it will boot :)

[TheKit]

sn is P820DBG2V5A02794, what does that mean?^^
Your tablet is ONDA V820W V5 then. Hardware like Wi-Fi/touchscreen/cameras might be different, but it should boot at least. You need to have 100 mb EFI partition and copy GRUB/kernel there, and ext4 root partition, large enough to contain Sailfish OS files.

I asked alredy Foxconn for Android Sources and Kernel but got of course no answer...

I have an second Nokia N1 (Chinese Modell), which i bought for spear parts....
I can try to flash Sailfish on it, or you think it wouldn't be so easy?
Are the devices identical hardware-wise? As first step, extract boot paritition from stock firmware. Try to repack it and make sure it can be booted (flash or boot directly via fastboot). Then try replacing kernel with the one found on Dell Venue 8 7840 Android 5.0 firmware and check if it still can boot (kernel modules won't match, but display driver is usually built into kernel).

[smatkovi]

Your tablet is ONDA V820W V5 then. Hardware like Wi-Fi/touchscreen/cameras might be different, but it should boot at least. You need to have 100 mb EFI partition and copy GRUB/kernel there, and ext4 root partition, large enough to contain Sailfish OS files.


Are the devices identical hardware-wise? As first step, extract boot paritition from stock firmware. Try to repack it and make sure it can be booted (flash or boot directly via fastboot). Then try replacing kernel with the one found on Dell Venue 8 7840 Android 5.0 firmware and check if it still can boot (kernel modules won't match, but display driver is usually built into kernel).

i don't know if they are identical. thanks for the ideas. why do i need the new kernel? for drivers? btw i broke ground on USB ,so ibrought it to arepair shop

[TheKit]

i don't know if they are identical. thanks for the ideas. why do i need the new kernel? for drivers? btw i broke ground on USB ,so ibrought it to arepair shop
I was replying to explit in second paragraph, please look at quotes.

[smatkovi]

I was replying to explit in second paragraph, please look at quotes.

Okay thanks, it was very late

[smatkovi]

Your tablet is ONDA V820W V5 then. Hardware like Wi-Fi/touchscreen/cameras might be different, but it should boot at least. You need to have 100 mb EFI partition and copy GRUB/kernel there, and ext4 root partition, large enough to contain Sailfish OS files.


Are the devices identical hardware-wise? As first step, extract boot paritition from stock firmware. Try to repack it and make sure it can be booted (flash or boot directly via fastboot). Then try replacing kernel with the one found on Dell Venue 8 7840 Android 5.0 firmware and check if it still can boot (kernel modules won't match, but display driver is usually built into kernel).

will the 6MB "kernel" file i extracted from boot.img do?

[smatkovi]

will the 6MB "kernel" file i extracted from boot.img do?

or can sb send me the contents of the boot partition?^^ it doesn't hurry though, because the tablet is still at the repair shop :D

[TheKit]

or can sb send me the contents of the boot partition?^^ it doesn't hurry though, because the tablet is still at the repair shop :D
You don't need boot partition. The kernel from /boot folder in rootfs is loaded using GRUB. We can't use Android bootloader, since UEFI is 32-bit and Jolla Tablet has 64-bit kernel (it's possible to compile 32-bit one, but I had some PulseAudio-related system crashes).

[smatkovi]

You don't need boot partition. The kernel from /boot folder in rootfs is loaded using GRUB. We can't use Android bootloader, since UEFI is 32-bit and Jolla Tablet has 64-bit kernel (it's possible to compile 32-bit one, but I had some PulseAudio-related system crashes).
so i just have to copy the files to a partition and install grub with reference reference to the kernel

[TheKit]

so i just have to copy the files to a partition and install grub with reference reference to the kernel
Exactly, no special installation is needed for GRUB, copying files to EFI partition is enough. If you want, I can try to make image for fastboot to flash Sailfish OS on ONDA.

[smatkovi]

Exactly, no special installation is needed for GRUB, copying files to EFI partition is enough. If you want, I can try to make image for fastboot to flash Sailfish OS on ONDA.
yes please :)

[TheKit]

yes please :)
Well, no luck with fastboot so far due to droidboot limitations and some problems with tools.

To make it easier, I did an improvised installer, based on Archiso and custom script. Just download the archive, extract it to the root of FAT32-formatted USB drive, and boot tablet from it:
https://mega.nz/#!8FZRiBwB!FBBD8CUMaBMkKcyiUDlw_sKfCjNZOQp713VqT-FoAhM

One thing though, the tablet of yours is ONDA V820W V5, while mine is V3. There are slight hardware changes, but I'm not sure what is different exactly. The image should boot, but touchscreen/Wi-Fi/Bluetooth/sound/etc may not work depending on what has been changed.

[smatkovi]

Well, no luck with fastboot so far due to droidboot limitations and some problems with tools.

To make it easier, I did an improvised installer, based on Archiso and custom script. Just download the archive, extract it to the root of FAT32-formatted USB drive, and boot tablet from it:
https://mega.nz/#!8FZRiBwB!FBBD8CUMaBMkKcyiUDlw_sKfCjNZOQp713VqT-FoAhM

One thing though, the tablet of yours is ONDA V820W V5, while mine is V3. There are slight hardware changes, but I'm not sure what is different exactly. The image should boot, but touchscreen/Wi-Fi/Bluetooth/sound/etc may not work depending on what has been changed.

thabk you very much :)

[smatkovi]

thanks, i did it :D with a few changes though, in grub.cfg you set russian locale i suppose, but it isn't there, so i commented that line, and wehere you mount the archiso for loopback i put a (hd0,1) before the $... oh and i forgot, i set the uuid manually

[smatkovi]

although after i made an update it cannot boot anymore :/

[smatkovi]

i know how to put back old sfos now, but i will try to replace the files from the overlay master zip over usb debugging

[smatkovi]

i don't know on what ip-address it listens and for which services, the phone listened on 192.168.2.15

[TheKit]

i don't know on what ip-address it listens and for which services, the phone listened on 192.168.2.15

It should listen at 192.168.2.15 port 2222 for telnet

[smatkovi]

It should listen at 192.168.2.15 port 2222 for telnet
thanks, i reverted the changes now and didn't update. okay, multitouch isn't working, sound isn't working at all and i cannot update. but i will use it because i want it mainly for sheet music

[TheKit]

thanks, i reverted the changes now and didn't update. okay, multitouch isn't working, sound isn't working at all and i cannot update. but i will use it because i want it mainly for sheet music

Can you post dmesg output of your tablet after booting? As I said, some hardware might be different.

[smatkovi]

will do when i'm at home :)

[mikecomputing]

What about SailfishOS on below :D

https://www.eevblog.com/2016/08/24/eevblog-914-sony-vaio-ux-micro-pc-teardown/

[TheKit]

What about SailfishOS on below :D

https://www.eevblog.com/2016/08/24/eevblog-914-sony-vaio-ux-micro-pc-teardown/

It's not impossible if you can get general Linux distro running on it. RAM amount might be an issue though.

[smatkovi]

Can you post dmesg output of your tablet after booting? As I said, some hardware might be different.

it's not a deb but there's a filesize limit. it's a plaintext file

[TheKit]

it's not a deb but there's a filesize limit. it's a plaintext file
Sorry, I meant to dump dmesg output right after booting the tablet so it's possible to check hardware initialization logs.

[smatkovi]

Sorry, I meant to dump dmesg output right after booting the tablet so it's possible to check hardware initialization logs.

oh, i rebooted now, here you go :)

[smatkovi]

being able to update would be great, sound and multitouch is not that important for me. funfact, i had to buy another tablet and they're both v5 but slightly different in design, the backplate isn't interchangeable and the little slid at the speaker became 2 slids instead of 1^^ i posted the things not working just in case anyone wants to know or do the same i want to do :)

[smatkovi]

maybe it's obvious, then tell me, but in case it's not: sound over Bluetooth is working

[TheKit]

being able to update would be great, sound and multitouch is not that important for me. funfact, i had to buy another tablet and they're both v5 but slightly different in design, the backplate isn't interchangeable and the little slid at the speaker became 2 slids instead of 1^^ i posted the things not working just in case anyone wants to know or do the same i want to do :)
I'll look into fixing problems with update/touch screen. Getting sound is harder, since for some reason there is a problem during kernel driver initialization on your hardware:
[ 3.768482] rt5640 2-001c: Failed to set private addr: -121
[ 3.783067] rt5640 2-001c: ASoC: mux INR Mux has no paths
[ 3.789147] rt5640 2-001c: ASoC: mux INL Mux has no paths

[smatkovi]

i had to reinstall and now i had only one partition on the whole usb-key, so i had to use (hd0) instead of (hd0,1)

[ferlanero]

i had to reinstall and now i had only one partition on the whole usb-key, so i had to use (hd0) instead of (hd0,1)

Hi! Any updates about waht is working and what not on this tablet? I have ordered one just now because I want to try Sailfish OS in a tablet :)

[TheKit]

Hi! Any updates about waht is working and what not on this tablet? I have ordered one just now because I want to try Sailfish OS in a tablet :)

Did you order Onda V820W or Onda V820W CH? Unfortunately, even if it's Onda V820W, there are at least 3 revisions (V1, V3 and V5) with different hardware. Mine is V3.

[ferlanero]

I have ordered Onda V820W V3 :) It arrives on next week :D

So mine will be v3 too, I think we can investigate together. How is the global perform of Sailfish here?

[TheKit]

I have ordered Onda V820W V3 :) It arrives on next week :D

So mine will be v3 too, I think we can investigate together. How is the global perform of Sailfish here?

The hardware mostly works, but I need to look into adapting better touch screen driver, as was discussed before, and try to implement OTA.

[ferlanero]

Hi guys! I'm trying to install your Sailfish port into a Onda v820w v3.

I have downloaded your image from Mega (https://mega.nz/#!8FZRiBwB!FBBD8CUMaBMkKcyiUDlw_sKfCjNZOQp713VqT-FoAhM)

Extracted it into a 4Gb USB 2.0 memory stick, but when I boot from that memory stick (which tablet recognises without any problem), the loader shows:

error: file /boot/grub/locale/ru.gmo not found

After that, the Grub loads trying to load the "archlinux-2016.08.13-flash-sfos.iso" but it fails again showing the next error:

error: file '/boot/archlinux-2016.08.13-flash-sfos.iso' not found.
error: disk 'loop' not found.
error: you need to load the kernel first.

Press any key to continue...

I can't figure what is wrong. Can you help me, please?

Thanks in advance!

[ferlanero]

Ok, first problem solved.

The

error: file /boot/grub/locale/ru.gmo not found

solved commenting the

set lang=ru_RU

line in grub.cfg

It should looks like:

# set lang=ru_RU

[ferlanero]

Second problem:

error: file '/boot/archlinux-2016.08.13-flash-sfos.iso' not found.
error: disk 'loop' not found.
error: you need to load the kernel first.

Press any key to continue...

Solved by changing line in grub.cfg

loopback loop $isofile

by

loopback loop (hd0,1)$isofile

And naming the USB memory stick as "USB"

[ferlanero]

I've just another question: after a succesfull instalation of the port in my Onda v820w v3 :D I received the 2.0.4.14 update. I tryed it, but after instalation, tablet didn't boot up. It stucks in a boot loop, anyone here coud make a successful update?

Thanks for your replies.

[juiceme]

I've just another question: after a succesfull instalation of the port in my Onda v820w v3 :D I received the 2.0.4.14 update. I tryed it, but after instalation, tablet didn't boot up. It stucks in a boot loop, anyone here coud make a successful update?

OTA updates on ported devices are usually not a breeze. I have tried that on Hammerhead and usually the results are not satisfactory; Probably the problem is that middleware changes prevent OS higher layer to work when some API's change slightly.

I recommend building it up from scratch, that's what I am doing.

[nodevel]

OTA updates on ported devices are usually not a breeze. I have tried that on Hammerhead and usually the results are not satisfactory; Probably the problem is that middleware changes prevent OS higher layer to work when some API's change slightly.

I recommend building it up from scratch, that's what I am doing.

I don't think this approach applies to Onda, because it is not a ported device in the sense of Hammerhead. It's a device that is closest to the Jolla Tablet, which has multiple implications. The main implication being all the proprietary stuff, which you will never be able to get on Hammerhead, works there out of the box (and that makes it very unique). The other implication is that you can't really build it from scratch, because you don't have sources to the proprietary stuff and you would instantly kill the uniqueness of Onda V820w if you tried to build it without them.

It is however worrying that there are differences between Jolla Tablet and Onda V820w that prevent smooth upgrade process.

[ferlanero]

I don't think this approach applies to Onda, because it is not a ported device in the sense of Hammerhead. It's a device that is closest to the Jolla Tablet, which has multiple implications. The main implication being all the proprietary stuff, which you will never be able to get on Hammerhead, works there out of the box (and that makes it very unique). The other implication is that you can't really build it from scratch, because you don't have sources to the proprietary stuff and you would instantly kill the uniqueness of Onda V820w if you tried to build it without them.

It is however worrying that there are differences between Jolla Tablet and Onda V820w that prevent smooth upgrade process.

That disappoint me :(

[smatkovi]

I've just another question: after a succesfull instalation of the port in my Onda v820w v3 :D I received the 2.0.4.14 update. I tryed it, but after instalation, tablet didn't boot up. It stucks in a boot loop, anyone here coud make a successful update?

Thanks for your replies.

hej, we talked about these 3 problems in the first few commnts after the upload of the modified os, we even talked about the singletouch only, do you expierience that too?

[ferlanero]

hej, we talked about these 3 problems in the first few commnts after the upload of the modified os, we even talked about the singletouch only, do you expierience that too?

Yes, only singletouch on my. It'd be great if we could investigate this issues on this tablet because everything else is working great!

[feedme]

would this run sfos
http://www.onda-tablet.com/onda-v919-air-dual-boot-tablet-pc-64gb.html

[TheKit]

would this run sfos
http://www.onda-tablet.com/onda-v919-air-dual-boot-tablet-pc-64gb.html
Not easy. The problem is missing kernel sources. Even though device is similar, no idea what is different in terms of drivers. Kernel bits need to be reverse-engineered, and as tortoisedoc tried on Teclast X98 Kindow, it can be pretty difficult.

Regarding Onda V820W V3, I'm currently trying to fix OTA. The idea is to properly repackage modified files, and see if there is a way to override some Jolla Tablet packages with Onda-specific adaptation during update.

Touch screen is a bigger problem, it seems. Currently open-source https://github.com/onitake/gslx680-acpi driver is used. It reports touch events as-is, without any software interpolation (which in theory should be the task for userspace). However, GSL1680 touch panel hardware is not very precise, so one touch gets reported as multiple touches with slighly different coordinates every time driver gets events from hardware.

The vendor driver for GSL1680 is more complicated, and while there is some source code, it won't work without changes for our device (currently it will crash the kernel). I'll see if I can do something about it, but no promises.

[ka9yhd]

The other day I saw this tablet from RCA at Walmart for $34.00. Any thoughts on it running Sailfish?

Chipset Model Number Intel SoFia 3GR 1.2Ghz Quad Core processor.

Doing a search for the specs on this tablet some sites claim it has a MT 8127 Quad core processor which is an Arm 7 processor. So I am not real sure if it is x86 or ARM?

https://rcaav.com/tablets/android/voyager-marshmallow/

[theonelaw]

Wishing you the very best luck,
But,
https://ubuntuforums.org/archive/index.php/t-2254725.html

[TheKit]

The other day I saw this tablet from RCA at Walmart for $34.00. Any thoughts on it running Sailfish?

https://rcaav.com/tablets/android/voyager-marshmallow/
Did a quick search and found out that at least earlier versions had bootloader locked. Also, even though RCA seems to be based in USA, I couldn't find kernel sources, which is GPL violation (Chinese companies usually don't care though).

[hardy_magnus]

The other day I saw this tablet from RCA at Walmart for $34.00. Any thoughts on it running Sailfish?

Chipset Model Number Intel SoFia 3GR 1.2Ghz Quad Core processor.

Doing a search for the specs on this tablet some sites claim it has a MT 8127 Quad core processor which is an Arm 7 processor. So I am not real sure if it is x86 or ARM?

https://rcaav.com/tablets/android/voyager-marshmallow/
I was surfing internet and found Ubislate i3G7 tablet with same specs and it has Intel x86 processor, hope it could run SFOS or native linux without android.
http://www.datawind.com/ubislate-i3g7.html

[TheKit]

I was surfing internet and found Ubislate i3G7 tablet with same specs and it has Intel x86 processor, hope it could run SFOS or native linux without android.
http://www.datawind.com/ubislate-i3g7.html
The same problems as with the tablet above.

In the meanwhile, I was checking what cheap Intel tablets have their kernel source code available and found this: https://github.com/bq/edison-3-mini. Pretty nice of BQ not only to provide source code, but also scripts for compilation. Porting Sailfish OS to it should be easy, yet, untortunately, BQ Edison 3 Mini is not available outside Spain.

[ka9yhd]

Thank you for the link and all thoughts on this device. And I will keep my eyes on the forums as to what works with Sailfish.

[mrsellout]

The same problems as with the tablet above.

In the meanwhile, I was checking what cheap Intel tablets have their kernel source code available and found this: https://github.com/bq/edison-3-mini. Pretty nice of BQ not only to provide source code, but also scripts for compilation. Porting Sailfish OS to it should be easy, yet, untortunately, BQ Edison 3 Mini is not available outside Spain.

Is this the same device?
http://www.ebay.co.uk/itm/bq-Edison-3-mini-8-16GB-Blanco-/222318294721?hash=item33c333f6c1:g:qXAAAOSwA3dYLjd t

[TheKit]

Is this the same device?
http://www.ebay.co.uk/itm/bq-Edison-3-mini-8-16GB-Blanco-/222318294721?hash=item33c333f6c1:g:qXAAAOSwA3dYLjd t

Seems to be.

[ferlanero]

hej, we talked about these 3 problems in the first few commnts after the upload of the modified os, we even talked about the singletouch only, do you expierience that too?

Yes I do. The singletouch is present on my device too

[ferlanero]

Would we have last update of Sailfish OS on Onda V820W V3? It would be nice because of good performance of this device with Sailfish :)

[TheKit]

Would we have last update of Sailfish OS on Onda V820W V3? It would be nice because of good performance of this device with Sailfish :)
Yeah, I have 2.0.5.6 running already (with the new approach of rebuilt packages), but I need to test it more thoroughly and look for possible upgrade path. Plan to do this on weekends.

[ferlanero]

Yeah, I have 2.0.5.6 running already (with the new approach of rebuilt packages), but I need to test it more thoroughly and look for possible upgrade path. Plan to do this on weekends.

Really good news :D If you need some help with testing, take in mind I have the same device ;)

[ferlanero]

The perform of the Onda V820W V3 with Sailfish 2.0.5.6 is absolutely incredible. It's an absolute pleasure manage Sailfish in big screens :)

[theonelaw]

The perform of the Onda V820W V3 with Sailfish 2.0.5.6 is absolutely incredible. It's an absolute pleasure manage Sailfish in big screens :)
Does wifi work ?

[ferlanero]

Does wifi work ?

Absolutely :) Everything works here

[smatkovi]

for you v3 users, does multitouch work for you?

[ferlanero]

for you v3 users, does multitouch work for you?

Yes, without any problem after helping of TheKit

[tmi]

If a person was planning to get a v820w Onda tablet would there be a way to make sure it actually is V3 (based on the assumption that V3 is the most compatible version regarding Sailfish... or Linux installations in general)? I suppose looking for Win8 + Android 4 instead of Win10 + Android 5 is a start but anything else?

[TheKit]

for you v3 users, does multitouch work for you?
You need to upgrade to 2.0.5.6. I ported touchscreen vendor's driver from a different tablet which supports multitouch. Please do backup in case something goes wrong, then follow the instructions below:

ssu re 2.0.5.6
ssu dr adaptation0
ssu dr adaptation1
ssu ar http://sfos.scanf.su/onda-v820w-v3/ adaptation-onda
ssu ur

version --dup

ssu dr adaptation0
ssu dr adaptation1
# Check if you still have adaptation-onda, if not - readd
ssu lr

# Remove old modules and reinstall device-specific packages:
rm /lib/modules/3.10.20/*.ko

zypper install -f droid-bin-tbj-onda-v820w-v3 droid-config-tbj-onda-v820w-v3 droid-config-tbj-onda-v820w-v3-flashing droid-config-tbj-onda-v820w-v3-kickstart-configuration droid-config-tbj-onda-v820w-v3-patterns droid-config-tbj-onda-v820w-v3-policy-settings droid-config-tbj-onda-v820w-v3-preinit-plugin droid-config-tbj-onda-v820w-v3-pulseaudio-settings droid-config-tbj-onda-v820w-v3-sailfish droid-config-tbj-onda-v820w-v3-ssu-kickstarts droid-hal-tbj-onda-v820w-v3 droid-hal-tbj-onda-v820w-v3-detritus droid-hal-tbj-onda-v820w-v3-kernel droid-hal-tbj-onda-v820w-v3-kernel-modules droid-hal-tbj-onda-v820w-v3-tools

depmod -a

# Check if you have graphics group and nemo is a member of it
cat /etc/group | grep graphics

# Should output "graphics:x:1003:nemo". If it's wrong for some reason, reinstall droid-hal-tbj-onda-v820w-v3 again



If a person was planning to get a v820w Onda tablet would there be a way to make sure it actually is V3 (based on the assumption that V3 is the most compatible version regarding Sailfish... or Linux installations in general)? I suppose looking for Win8 + Android 4 instead of Win10 + Android 5 is a start but anything else?

You could try to ask the seller for device serial number located at the back side. For example, see this photo (http://irecommend.ru/sites/default/files/imagecache/copyright1/user-images/113588/rSgU1gSz2FhXKr8zxR6sOQ.jpg). It's P820DBF4V3...

[sunburnedpenguin]

@TheKit You're awesome for helping move the reality of a working SalifishOS tablet closer to being realised!

Does anyone recommend a source for the v3 Onda? I've found it offered on multiple sites (geekbuying.com, everbuying.net, etc.) but am not certain as to their reputation. Is it best to try and buy off eBay?

Thanks!

[TheKit]

Does anyone recommend a source for the v3 Onda? I've found it offered on multiple sites (geekbuying.com, everbuying.net, etc.) but am not certain as to their reputation. Is it best to try and buy off eBay?
Thanks!

I think it doesn't matter much as long as you can get right model. eBay and sites like jd.com, gearbest.com, geekbuying.com should be safe enough, but better pay with PayPal just in case. Local stock is preferred probably.

[itdoesntmatt]

i strongly suggest to avoid gearbest. bad experiences with them, poor customer assistance, i had to really fight to have my rights respected

[smatkovi]

great, i could update my v5 and multitouch is working as well now, great job, thanks :) You need to upgrade to 2.0.5.6. I ported touchscreen vendor's driver from a different tablet which supports multitouch. Please do backup in case something goes wrong, then follow the instructions below:

ssu re 2.0.5.6
ssu dr adaptation0
ssu dr adaptation1
ssu ar http://sfos.scanf.su/onda-v820w-v3/ adaptation-onda
ssu ur

version --dup

ssu dr adaptation0
ssu dr adaptation1
# Check if you still have adaptation-onda, if not - readd
ssu lr

# Remove old modules and reinstall device-specific packages:
rm /lib/modules/3.10.20/*.ko

zypper install -f droid-bin-tbj-onda-v820w-v3 droid-config-tbj-onda-v820w-v3 droid-config-tbj-onda-v820w-v3-flashing droid-config-tbj-onda-v820w-v3-kickstart-configuration droid-config-tbj-onda-v820w-v3-patterns droid-config-tbj-onda-v820w-v3-policy-settings droid-config-tbj-onda-v820w-v3-preinit-plugin droid-config-tbj-onda-v820w-v3-pulseaudio-settings droid-config-tbj-onda-v820w-v3-sailfish droid-config-tbj-onda-v820w-v3-ssu-kickstarts droid-hal-tbj-onda-v820w-v3 droid-hal-tbj-onda-v820w-v3-detritus droid-hal-tbj-onda-v820w-v3-kernel droid-hal-tbj-onda-v820w-v3-kernel-modules droid-hal-tbj-onda-v820w-v3-tools

depmod -a

# Check if you have graphics group and nemo is a member of it
cat /etc/group | grep graphics

# Should output "graphics:x:1003:nemo". If it's wrong for some reason, reinstall droid-hal-tbj-onda-v820w-v3 again





You could try to ask the seller for device serial number located at the back side. For example, see this photo (http://irecommend.ru/sites/default/files/imagecache/copyright1/user-images/113588/rSgU1gSz2FhXKr8zxR6sOQ.jpg). It's P820DBF4V3...

[smatkovi]

okay, the camera stopped working, but i don't care because i don't use it anyway, just fyi great, i could update my v5 and multitouch is working as well now, great job, thanks :)

[smatkovi]

here is the dmesg output of the updated v5 in case you're interested :)

[tmi]

You could try to ask the seller for device serial number located at the back side. For example, see this photo (http://irecommend.ru/sites/default/files/imagecache/copyright1/user-images/113588/rSgU1gSz2FhXKr8zxR6sOQ.jpg). It's P820DBF4V3...

Thanks, I did... with mixed results. Not everyone answered, some were sold out and one seller claimed he could not give me this information since the S/N changes on every tablet (even though I only asked to check if the 9th & 10th digits were V3 or V5) :D

I ended up ordering from here (http://www.ainol-novo.com/onda-v820w-dual-os-32gb-white.html) (EDIT: was sold out, after all). ATM it was the only Win 8.1 version I could find available and I figured the chances for V3 would be higher there, but let's see what I end up actually getting.)

EDIT: Seems like V3 are non-existent for now and even V5 are getting scarcer as many sellers reported having sold-out. Ordered one V5 (according to the seller) from eBay. We'll see...

[bomo]

I think it doesn't matter much as long as you can get right model. eBay and sites like jd.com, gearbest.com, geekbuying.com should be safe enough, but better pay with PayPal just in case. Local stock is preferred probably.

As also tmi said that V3 is currently very hard to find, I want to ask you directly: Is the only problem of V5 and (V6? or V7?) that you are not sure whether your port works there or are you sure that further adaptions are needed due to hardware changes in these revisions?

[TheKit]

As also tmi said that V3 is currently very hard to find, I want to ask you directly: Is the only problem of V5 and (V6? or V7?) that you are not sure whether your port works there or are you sure that further adaptions are needed due to hardware changes in these revisions?
I'm sure futher adaptations are needed for V5 (sound doesn't work, only through Bluetooth). No idea about V7 (the golden one), since no one had it here before.

[tmichel]

Hi,

I just received a V820W, sadly the Version 5.

However, Sailfish OS intallation went smoothly, needed two tries for the update to 2.0.5.4 but now it's running. Audio does not work, neither does bluetooth (cannot be enabled).

Had some trouble to get into WiFi at the beginning as I could not see the scanning results - it seemed I could not scroll down in the Result window, possibly a graphics issue. Managed to get it working using connmanctl.

Two things I noticed on the installer: First, it does install to NAND, not to the SDCard (probably my mistake, I did not understood that in the description). So bye-bye to Windows and Android :-)

Second, the installer creates a 10 GB partition though the device has 32 GB which renders the 20 GB useless. Maybe I try to reinstall Windows 10 on it or make it a seperate /home partition.

Thanks to all the porters!

[tmi]

I'd guess the 10GB partition could be resized with gparted.
Here (https://medium.com/@tomac/installing-ubuntu-mint-linux-on-onda-820w-tablet-727747a376b#.4b93nkiic) are instructions for installing Linux Mint on the tablet featuring also the makings of a bootable USB flashdrive (including gparted).

[TheKit]

Hi,

I just received a V820W, sadly the Version 5.

However, Sailfish OS intallation went smoothly, needed two tries for the update to 2.0.5.4 but now it's running. Audio does not work, neither does bluetooth (cannot be enabled).

Could you try rebooting and then enabling Bluetooth by single tap in settings? There is some race-condition with rkfill and hciattach.

On a side note, I see there is a newer and (probably) easier to get Onda V80 SE (http://www.gearbest.com/tablet-pcs/pp_429776.html?wid=21) with the same SoC, but hard to say how different is it.

[tmichel]

[QUOTE=TheKit;1521772]Could you try rebooting and then enabling Bluetooth by single tap in settings? There is some race-condition with rkfill and hciattach.

Hi,same problem, Bluetooth icon is just blinking. While BT is of, I get lots off errors in the journal:


Jan 11 13:01:58 Sailfish kernel: RTL871X: IsBtDisabled=0, IsBtControlLps=0
Jan 11 13:01:58 Sailfish kernel: RTL871X: (+)Tx = 0, Rx = 0
Jan 11 13:01:58 Sailfish kernel: RTL871X: CurIGValue=41, EntryMinUndecoratedSmoothedPWDB = 36
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet
Jan 11 13:01:59 Sailfish kernel: Bluetooth: Controller acked invalid packet


Trying to switch it on results in:

Jan 11 13:02:02 Sailfish bluetooth_rfkill_event[394]: main(bluetooth_rfkill_event.c:1136): BT power driver blocked
Jan 11 13:02:02 Sailfish bluetooth_rfkill_event[394]: free_hci(bluetooth_rfkill_event.c:785): No brcm_patchram_plus process to be found
Jan 11 13:02:02 Sailfish bluetooth_rfkill_event[394]: main(bluetooth_rfkill_event.c:1138): BT disabled
Jan 11 13:02:02 Sailfish kernel: RTL871X: IsBtDisabled=0, IsBtControlLps=0
Jan 11 13:02:02 Sailfish kernel: RTL871X: (+)Tx = 0, Rx = 0
Jan 11 13:02:02 Sailfish kernel: RTL871X: CurIGValue=41, EntryMinUndecoratedSmoothedPWDB = 37
Jan 11 13:02:04 Sailfish kernel: RTL871X: IsBtDisabled=0, IsBtControlLps=0
Jan 11 13:02:04 Sailfish kernel: RTL871X: (+)Tx = 0, Rx = 0
Jan 11 13:02:04 Sailfish kernel: RTL871X: CurIGValue=41, EntryMinUndecoratedSmoothedPWDB = 39
Jan 11 13:02:06 Sailfish kernel: RTL871X: IsBtDisabled=0, IsBtControlLps=0
Jan 11 13:02:06 Sailfish kernel: RTL871X: (+)Tx = 1, Rx = 1
Jan 11 13:02:06 Sailfish kernel: RTL871X: CurIGValue=41, EntryMinUndecoratedSmoothedPWDB = 36
Jan 11 13:02:08 Sailfish kernel: RTL871X: IsBtDisabled=0, IsBtControlLps=0
Jan 11 13:02:08 Sailfish kernel: RTL871X: (+)Tx = 0, Rx = 0
Jan 11 13:02:08 Sailfish kernel: RTL871X: CurIGValue=41, EntryMinUndecoratedSmoothedPWDB = 36
Jan 11 13:02:10 Sailfish kernel: RTL871X: YJ: rtl8723b_fill_default_txdesc(): ARP Data: userate=1, datarate=0x0

These arrors com multiple times.

[bomo]

On a side note, I see there is a newer and (probably) easier to get Onda V80 SE (http://www.gearbest.com/tablet-pcs/pp_429776.html?wid=21) with the same SoC, but hard to say how different is it.

Thanks for the hint, can you elaborate what else, besides the SoC is important with respect to using the current port / portability in general? I (naively) assumed that the drivers can be taken from Android and used via libhybris.

[TheKit]

Thanks for the hint, can you elaborate what else, besides the SoC is important with respect to using the current port / portability in general? I (naively) assumed that the drivers can be taken from Android and used via libhybris.
There are two kinds of drivers: kernel drivers and libs in userspace. The second kind can be used via libhybris. Kernel drivers are supposed to be open-source due to license of Linux kernel, but Chinese manufacturers don't care about GPL.

Android kernel binary can't be used directly for SailfishOS (kernel needs recompiling with different options). So without having kernel tree source code the only option is using kernel source tree from different device and fixing the differences (different components or different pinouts, for example) by reverse-engineering stock kernel.

[smatkovi]

yes, i asked for an installer to nand instead of sdcard. i made a new partition with the remaining space and mounted it under a folder i created in /home/nemo/ (i always mix up /home/user/MyDocs/ and /home/nemo/ i hope that is right)
Hi,

I just received a V820W, sadly the Version 5.

However, Sailfish OS intallation went smoothly, needed two tries for the update to 2.0.5.4 but now it's running. Audio does not work, neither does bluetooth (cannot be enabled).

Had some trouble to get into WiFi at the beginning as I could not see the scanning results - it seemed I could not scroll down in the Result window, possibly a graphics issue. Managed to get it working using connmanctl.

Two things I noticed on the installer: First, it does install to NAND, not to the SDCard (probably my mistake, I did not understood that in the description). So bye-bye to Windows and Android :-)

Second, the installer creates a 10 GB partition though the device has 32 GB which renders the 20 GB useless. Maybe I try to reinstall Windows 10 on it or make it a seperate /home partition.

Thanks to all the porters!

[smatkovi]

did anyone of you manage to get play services working?

[tmichel]

did anyone of you manage to get play services working?

Hi,

it works just fine. I followed the instructions on TJC for the Jolla tablet if I remember correctly.

[smatkovi]

Hi,

it works just fine. I followed the instructions on TJC for the Jolla tablet if I remember correctly.

so you can use google maps integrated in other apps for instance?

[tmi]

I got my V820W V5 a couple of weeks back but only now have had some time to toy with it.

With the automatic installer from the first post I got Sailfish on the tablet yesterday - only needed to comment out the Russian locale (maybe worth a mention in the first post?)

Ironically, sfos.scanf.su site was down at the time so I wasn't able then to update to 2.0.5.6 using TheKit's instructions (http://talk.maemo.org/showpost.php?p=1520799&postcount=82) on page 9, so I tried the tablet as it was. Due to a bunch of little annoyances I was a bit disappointed (had trouble with the wifi, the system time wouldn't update neither could be set correctly, ambience setting would reset after boot etc). Today, I could finally run all the commands to update to 2.0.5.6. (Some files were not found in the Jolla repository and I had to choose 'ignore' 3-4 times near the end but it didn't seem to hinder anything.)

After the boot... color me impressed! Using the tablet feels pretty sweet even though the sound is not working (which was expected). I'm not claiming that everything else works 100% as I've not used it that much yet, but I haven't really found a reason to complain, either. For roughly 80 euros the tablet already seems like a more than adequate substitute for a real Jolla Tablet where I'm concerned... others may have different opinions, of course.
Great work TheKit!

I did update the tablet's BIOS in hopes of maybe getting the sound to work as I read somewhere that this update (http://chinagadgetsreviews.blogspot.com/2016/01/download-latest-bios-upgrade-file-for.html) will fix it for Android. No such luck with Sailfish.

Another thing I haven't been able to do is install Linux on the tablet. I've tried with different versions of Linux Mint but the display keeps staying blank after boot despite tries with different parameters e.g. 'i915.modeset=0', 'nomodeset', 'grub_gfxmode=1280x800x24', 'acpi_osi=Linux', 'i915.broken=1 i915.alse_backlight=1' etc.

[TheKit]

Another thing I haven't been able to do is install Linux on the tablet. I've tried with different versions of Linux Mint but the display keeps staying blank after boot despite tries with different parameters e.g. 'i915.modeset=0', 'nomodeset', 'grub_gfxmode=1280x800x24', 'acpi_osi=Linux', 'i915.broken=1 i915.alse_backlight=1' etc.
Did you try i915.fastboot=1 with 4.7 or 4.8 kernel? The very latest ones probably need hack mentioned there (https://bugs.freedesktop.org/show_bug.cgi?id=96996).

[tmi]

Did you try i915.fastboot=1 with 4.7 or 4.8 kernel? The very latest ones probably need hack mentioned there (https://bugs.freedesktop.org/show_bug.cgi?id=96996).

Thank you for this! I managed to boot Linux Mint 18.1 with quiet splash removed and i915.fastboot=1 added.
(EDIT: removed the video parameter as I don't seem to need it, after all)

I noticed the screen won't turn and I have't tried installing but at least now there's a way to use GParted for e.g. enlarging the sailfishos partition size if needed.

[TheKit]

Thank you for this! I managed to boot Linux Mint 18.1 with quiet splash removed and i915.fastboot=1 video=1280x800@60 added.

I noticed the screen won't turn and I have't tried installing but at least now there's a way to use GParted for e.g. enlarging the sailfishos partition size if needed.
Do you have sound in Mint or anything about sound chip in dmesg?

[tmi]

Do you have sound in Mint or anything about sound chip in dmesg?

Unfortunately, no sound. Here (http://pastebin.com/fkvF8vhQ) is the dmesg output after boot, didn't see any mention of rt5640, though.

[TheKit]

Unfortunately, no sound. Here (http://pastebin.com/fkvF8vhQ) is the dmesg output after boot, didn't see any mention of rt5640, though.
[ 38.438878] sst-acpi 80860F28:00: No matching ASoC machine driver found

Yeah, not really helpful. If someone still has Android on V5, would be good to get dmesg from it.

[smatkovi]

[ 38.438878] sst-acpi 80860F28:00: No matching ASoC machine driver found

Yeah, not really helpful. If someone still has Android on V5, would be good to get dmesg from it.

did any of you try "installing" the driver or is it even possible in sfos to install drivers like in linux?

[TheKit]

did any of you try "installing" the driver or is it even possible in sfos to install drivers like in linux?
Well, on V5 we're missing sound codec driver and machine driver for that codec. It's implemented in kernel, so it can't be easily "installed" both in Linux or SFOS.

DSDT dump can be useful to at least identify the codec:
cat /sys/firmware/acpi/tables/DSDT > DSDT.aml

[tmichel]

so you can use google maps integrated in other apps for instance?

Not sure what you mean by that? Maps and Google Earth work fine, aso some other apps that use play services to my knowledge.

[smatkovi]

Not sure what you mean by that? Maps and Google Earth work fine, aso some other apps that use play services to my knowledge.

i mean like an app for public transport which shows you the route on a google maps map integrated into this app

[tmichel]

i mean like an app for public transport which shows you the route on a google maps map integrated into this app

Can't tell, the only app that I have installed doing this is the German telephony book, but that seems to get it's data from Here Maps; which works.

If you give me an example app, I can install and test.

[smatkovi]

lol, for example scotty mobil or anachb, citybike wien...

[smatkovi]

do you use das örtliche ?

[tmichel]

do you use das örtliche ?

Yes, that works fine including showing maps.

[smatkovi]

Yes, that works fine including showing maps.

ok,for me it works too

[smatkovi]

i tried to update to newest version as suggested here, not the version mentioned here but the most recent, but it didn't work. did anyone of you try to update

[Flos]

Hi,

I can install the sailfish os into my v820w with your installer. That's so wonderful!! But after I boot up the pad and tried to increase the sound volume, I find the sound card doesn't work. Then I change the music of the ring tone in the UI, still silence. I grab some log from the system log as follows, could you please help to look into this?


$ grep rt564 messages.out
Mar 04 21:16:03 Jolla kernel: snd_byt_bl_rt5642: Baytrail Machine Driver byt_rt5642 registerd
Mar 04 21:16:03 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:03 Jolla kernel: byt_rt5642 AMCR0F28:00: rt5640-aif1 <-> Headset-cpu-dai mapping ok
Mar 04 21:16:03 Jolla kernel: byt_rt5642 AMCR0F28:00: rt5640-aif2 <-> Voice-cpu-dai mapping ok
Mar 04 21:16:03 Jolla kernel: compress asoc: rt5640-aif1 <-> Compress-cpu-dai mapping ok
Mar 04 21:16:03 Jolla kernel: byt_rt5642 AMCR0F28:00: snd-soc-dummy-dai <-> ssp-bt-cpu-dai mapping ok
Mar 04 21:16:03 Jolla kernel: byt_rt5642 AMCR0F28:00: snd-soc-dummy-dai <-> ssp-modem-cpu-dai mapping ok
Mar 04 21:16:03 Jolla kernel: rt5640 2-001c: ASoC: mux INR Mux has no paths
Mar 04 21:16:03 Jolla kernel: rt5640 2-001c: ASoC: mux INL Mux has no paths
Mar 04 21:16:03 Jolla kernel: snd_byt_bl_rt5642: snd_byt_mc_probe successful
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Mono ADC MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo ADC MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Mono ADC MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo ADC MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: RECMIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: RECMIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPOR MIX DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPOL MIX DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Mono ADC MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo ADC MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Mono ADC MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo ADC MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: RECMIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: RECMIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPOR MIX DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: SPOL MIX DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXL DAPM update failed: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:11 Jolla kernel: rt5640 2-001c: Failed to read private reg: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: Failed to read private reg: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXR DAPM update failed: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXL DAPM update failed: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: ASoC: SPOR MIX DAPM update failed: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: ASoC: SPOL MIX DAPM update failed: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:16:13 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXL DAPM update failed: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXR DAPM update failed: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXL DAPM update failed: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: ASoC: SPOR MIX DAPM update failed: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: ASoC: SPOL MIX DAPM update failed: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: Failed to read private reg: -121
Mar 04 21:16:18 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXL DAPM update failed: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: Failed to read private reg: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXR DAPM update failed: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXL DAPM update failed: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: ASoC: SPOR MIX DAPM update failed: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: ASoC: SPOL MIX DAPM update failed: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:16:22 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXL DAPM update failed: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXR DAPM update failed: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXL DAPM update failed: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: ASoC: SPOR MIX DAPM update failed: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: ASoC: SPOL MIX DAPM update failed: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXL DAPM update failed: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:17:12 Jolla kernel: rt5640 2-001c: Failed to read private reg: -121
Mar 04 21:17:20 Jolla kernel: rt5640 2-001c: Failed to set private addr: -121
Mar 04 21:17:20 Jolla kernel: rt5640 2-001c: Failed to read private reg: -121
Mar 04 21:17:20 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXR DAPM update failed: -121
Mar 04 21:17:20 Jolla kernel: rt5640 2-001c: ASoC: SPK MIXL DAPM update failed: -121
Mar 04 21:17:21 Jolla kernel: rt5640 2-001c: ASoC: SPOR MIX DAPM update failed: -121
Mar 04 21:17:21 Jolla kernel: rt5640 2-001c: ASoC: SPOL MIX DAPM update failed: -121
Mar 04 21:17:21 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXR DAPM update failed: -121
Mar 04 21:17:21 Jolla kernel: rt5640 2-001c: ASoC: Stereo DAC MIXL DAPM update failed: -121


Thanks again!

[TheKit]

i tried to update to newest version as suggested here, not the version mentioned here but the most recent, but it didn't work. did anyone of you try to update
I need to rebuild packages for 2.1.0.9. Planned to do once it's out of early access.

Hi,
But after I boot up the pad and tried to increase the sound volume, I find the sound card doesn't work. Then I change the music of the ring tone in the UI, still silence. I grab some log from the system log as follows, could you please help to look into this?
Could you please confirm your revision? Is it V3, V5 or something else? Check the digit after letter "V" in serial number at the back of the tablet.

[smatkovi]

i got google services working by installing the oldest version for jolla tablet and updating afterwards

[Flos]

Could you please confirm your revision? Is it V3, V5 or something else? Check the digit after letter "V" in serial number at the back of the tablet.

Ahh.. yes, you're right, it shuld be a V5. The full string is:

P820DBFBV5A01619

So, any chance I can bring the sound back? Thanks!

[TheKit]

Ahh.. yes, you're right, it shuld be a V5. The full string is:

P820DBFBV5A01619

So, any chance I can bring the sound back? Thanks!
No easy way, since it's a known issue due to V5 having different sound codec. I didn't see those errors before though. Could you please provide full dmesg log after boot (upload as file or to pastebin) and DSDT tables dump:
cat /sys/firmware/acpi/tables/DSDT > dsdt.dat

[Flos]

Hi TheKit, please kindly find the file in the attachment. Thanks!

[TheKit]

Hi TheKit, please kindly find the file in the attachment. Thanks!

Thanks for the logs. I did some investigation in spare time. DSDT is almost the same with V3. I downloaded Android firmwares for both revisions and compared their kernels with BinDiff to see if there are changes in sound codec or SST drivers. Surprisingly, there are no obvious differences in code, which means it might be data that's different.

I compared rt5640_init_reg array in kernel binaries and found exactly one change:

{RT5640_HPO_MIXER, 0xc000}, /*HPVOL -> HPOLMIX */
/*{RT5640_HPO_MIXER, 0xa000},//DAC1 -> HPOLMIX*/

V3 sets RT5640_HPO_MIXER to 0xc000 and V5 sets it to 0xa000 instead, which was present, but commented out in available kernel source tree.

I presume this won't be the only change, but I want V5 owners to test this kernel (http://sfos.scanf.su/onda-v820w-v3/kernel-v5-test.zip) and post dmesg before I go further.

devel-su
mkdir /boot/esp
mount /dev/mmcblk0p1 /boot/esp
mv /boot/esp/bzImage /boot/esp/bzImage-old
cp bzImage /boot/esp/bzImage
reboot

[tmi]

I want V5 owners to test this kernel (http://sfos.scanf.su/onda-v820w-v3/kernel-v5-test.zip) and post dmesg before I go further.


Here's pastebin (http://pastebin.com/Qr8SwmaW) from mine.
I just want to say, I really appreciate what you're doing here!

[TheKit]

Here's pastebin (http://pastebin.com/Qr8SwmaW) from mine.
I just want to say, I really appreciate what you're doing here!
Thank you! Now that's different from other devices, rt5642 codec isn't detected on I2C. Could you please also upload your DSDT?
cat /sys/firmware/acpi/tables/DSDT > dsdt.dat

[tmi]

Could you please also upload your DSDT?


Sure. /10char

[tmichel]

Hi,

find attached anoterh dmesg and dsdt from an Onda V5.

[TheKit]

@tmi, @tmichel your device has rt5651 codec, as opposed to rt5642 on V3 (and some other V5?). Newer kernel has driver for rt5651 codec, but likely it won't be easy to backport to 3.10. Wish there was a way to get actual kernel source used for the tablet.

[smatkovi]

here's mine, as usual i just added the extension because of the filesize edit: experimental kernel with audio

[smatkovi]

i encountered a bug, the accelerometer stopped working for me with the experimental kernel

[tmi]

i encountered a bug, the accelerometer stopped working for me with the experimental kernel

I can verify this as I just realized the same. Copying the old kernel back + reboot makes the display rotate again.

[smatkovi]

but i would change the kennel to listen to music and then back, that would be no problem for me, i think better than no sound at all

[ferlanero]

Hi! Is there any chance of seeing Sailfish 2.1 running in our beloved Onda V820W V3? This tablet port is the only real Sailfish tablet experience (despite the oficial Jolla Tablet) out there for who likes to ban Android away their lifes!

[explit]

I got pretty much inspired by https://jolla.comes.today/jolla-tablet-on-taobao-china/ article and firmware from http://talk.maemo.org/showthread.php?t=96474. In a nutshell, official Jolla Tablet is a device based around Intel Atom Z3735F SoC (Bay Trail) and can work both with Sailfish OS and Android (by the way, Android device tree it's based on is called "anzhen4_mrd8_w").

There have been a lot of cheap Chinese tablet using the same SoC, and usually they come with Android/Windows dualboot. So what's preventing us from running Sailfish OS on them? Android firmware can often be easily ported between such devices, but kernel is device-specific, so custom ROM makers just use the stock kernel from their device unmodified.

For Sailfish OS, we can't, since systemd requires some kernel options which are most of time turned off in Android kernels. Enabling them and recompiling kernel would be easy if Chinese manufacturers didn't violate GPL and actually provided kernel sources, but that's not the case. Thankfully, since most of hardware is similar, it's possible to base custom kernel on other device source.

I have Sailfish OS running on Onda V820w tablet. It's not perfect yet, but the hardware itself (touchscreen, audio, Wi-Fi, Bluetooth, front and back cameras) works. Many thanks to Stskeeps for providing modules folders which were missing from Jolla Tablet kernel sources. The biggest problem was getting kernel working with camera sensors. Even though the needed drivers are present, PMIC regs and GPIO pin meanings turned out to be different. Just a few values to change, but it was very troublesome to debug and I had to disassemble Onda stock Android kernel to understand what's wrong.

Below is a guide to installing Sailfish OS on Onda V820w (tested with V3, see serial number to understand what revision is yours if you happen to have it). Hope community will be interested in running Sailfish OS on other similar devices and we can have more supported. I'm happy to help with what I can either here or at #sailfishos-porters on IRC.



Update: automatic installer (all data is going to be erased!) image for ONDA V820W V3: https://mega.nz/#!8FZRiBwB!FBBD8CUMaBMkKcyiUDlw_sKfCjNZOQp713VqT-FoAhM. Unpack it to the root of FAT32 formatted USB drive and boot tablet from USB drive.
How do you think are the chances to get your image running on another Baytrail tablet Medion Lifetab S10366?
Its also based on anzhen Android Device Tree.

Here is my post about it:
http://talk.maemo.org/showthread.php?t=99355

Thanks

[TheKit]

How do you think are the chances to get your image running on another Baytrail tablet Medion Lifetab S10366?
Its also based on anzhen Android Device Tree.

Here is my post about it:
http://talk.maemo.org/showthread.php?t=99355

Thanks
I think the way it runs on ONDA is more hacky and complicated than it probably needs to be for Medion, if it's based on same device tree. Onda has 32-bit UEFI firmware and no kernel source code available from vendor, so basically I adapted Jolla Tablet kernel tree for it and used GRUB2 bootloader to boot 64-bit kernel with 32-bit UEFI (32-bit kernel can be also used in theory, but there is weird bug with kernel panic on starting PulseAudio).

Since Medion is Germany-based, can you request GPL kernel source code from them? It's either not present on their website or I couldn't find it.

[explit]

This was really easy.
You can download Android 5.1.1 Sources for Medion just on their Website....

http://www1.medion.de/downloads/download.pl?lang=de&filename=s1036x-5.1.1-source.tar.gz&id=17011&type=quellcode

Can you use them also for Onda?

[eugl]

I think the way it runs on ONDA is more hacky and complicated than it probably needs to be for Medion, if it's based on same device tree. Onda has 32-bit UEFI firmware and no kernel source code available from vendor, so basically I adapted Jolla Tablet kernel tree for it and used GRUB2 bootloader to boot 64-bit kernel with 32-bit UEFI (32-bit kernel can be also used in theory, but there is weird bug with kernel panic on starting PulseAudio).

Since Medion is Germany-based, can you request GPL kernel source code from them? It's either not present on their website or I couldn't find it.

Hello TheKit! Tell me, please, whether it is possible to port sailfishos on a tablet having a dual load. My tablet on an Intel Atom X3 C3230 processor (zenpad c7 z170cg). Can I use the firmware that you prepared for the Onda 830 without modification to be installed on my tablet?

[eugl]

Hello TheKit! Tell me, please, whether it is possible to port sailfishos on a tablet having a dual load. My tablet on an Intel Atom X3 C3230 processor (zenpad c7 z170cg). Can I use the firmware that you prepared for the Onda 830 without modification to be installed on my tablet?

[eugl]

I think the way it runs on ONDA is more hacky and complicated than it probably needs to be for Medion, if it's based on same device tree. Onda has 32-bit UEFI firmware and no kernel source code available from vendor, so basically I adapted Jolla Tablet kernel tree for it and used GRUB2 bootloader to boot 64-bit kernel with 32-bit UEFI (32-bit kernel can be also used in theory, but there is weird bug with kernel panic on starting PulseAudio).

Since Medion is Germany-based, can you request GPL kernel source code from them? It's either not present on their website or I couldn't find it.

Hello TheKit! Tell me, please, whether it is possible to port sailfishos on a tablet having a dual load. My tablet on an Intel Atom X3 C3230 processor (zenpad c7 z170cg). Can I use the firmware that you prepared for the Onda 830 without modification to be installed on my tablet?

[tmi]

Hi! Is there any chance of seeing Sailfish 2.1 running in our beloved Onda V820W V3?

I assume there's been no change in this issue lately?

(I admit I haven't been paying attention very closely as I've used my Onda quite sparingly.
Sure, there is the Youyota tablet option and I might still actually end up getting one but in the meantime I will also gladly welcome any possible SFOS updates for Onda.)

[ferlanero]

I love to use my Onda V820W V3 with SailfishOS. By far, the best OS for tablets without doubt. Almost a year using the Onda and quite happy with it. Now I've backed th Youyota so I hope I can use Sailfish for at least another year! :)

[dubliner]

Excited by the idea to run SFOS on a tablet, I ordered myself an Onda V820w V3 which just arrived today.

Problem: I am stuck in an infinite boot loop. :(

What I did: I used the automatic installer including ferlanero's suggestions mentioned in posts #54 and #55. Installation finished with a reboot. After that, all I see is the GRUB menu "Sailfish OS" or "Sailfish OS (USB debug mode)" which, when selected (either one), results in a black screen and a reboot.

Can anyone help, please?

[TheKit]

Excited by the idea to run SFOS on a tablet, I ordered myself an Onda V820w V3 which just arrived today.

Problem: I am stuck in an infinite boot loop. :(
Is it Onda V820W, not Onda V820W CH? Not sure if original one can be found anymore in shops.

[dubliner]

Thanks for the quick reply, TheKit!!!

I bought it used. The SN starts with P820DBF4V3A... and the package doesn't say anything about CH.

Sticker:
Onda V820W DualOS 32GB
Screen: 8.0inch display (1280x800resolution)
CPU: Intel Z3735F,64-bit,2M Cahce, up to 1.83 GHz
GPU: Intel HD Graphics
...

P.S. Argh, Sticker may not belong to tablet since it has a different SN (for V1). But the SN quoted above is on the tablet itself.

P.P.S. How would a regular V3 serial number start?

P.P.P.S. It's working now!!! All I had to do was to reset BIOS to default! Man, this was stressful... :D

[TheKit]

P.P.P.S. It's working now!!! All I had to do was to reset BIOS to default! Man, this was stressful... :D
Did you boot Windows before installing it? UEFI has "Android" and "Windows" modes with different quirks to boot them.

[dubliner]

Thanks again for the quick reply, TheKit! I owe you one!

Yes, I did boot into Windows first, basically just to check whether the device was working at all.

One thing I noticed: When I first charged it, a red LED lit up. It no longer seems to do this. Yet, SFOS reported "charging". Is that normal?

Would it be possible to add some information like posts #54/#55, the serial number and the BIOS reset thing to the first message in this thread? Future users might appreciate this.

BTW, I'm just running the 2.0.5.6 upgrade (19%... fingers crossed!). Are there any chances for a 2.1.x upgrade?

[dubliner]

Here's a funny thing after the upgrade from the installer image to 2.0.5.6.

Instead of the normal "unlock" screen with the "> <" symbols I now just get a black screen with the rotating circle. :confused: At first I thought Lipstick hadn't started until I tried swiping.

Is there a method to remedy?

[TheKit]

One thing I noticed: When I first charged it, a red LED lit up. It no longer seems to do this. Yet, SFOS reported "charging". Is that normal?

BTW, I'm just running the 2.0.5.6 upgrade (19%... fingers crossed!). Are there any chances for a 2.1.x upgrade?

I didn't reverse the kernel part to light that red LED, since on Android it's only lit when charging, so this can be ignored.

I planned to update it to 2.1.x, but still didn't do it. Will try to check it again.

Instead of the normal "unlock" screen with the "> <" symbols I now just get a black screen with the rotating circle.[/B] :confused: At first I thought Lipstick hadn't started until I tried swiping.

Is there a method to remedy?

That's weird. I didn't see this on tablet. Usually this happens when it's waiting for ofono, but we don't have telephony.

[dubliner]

I didn't reverse the kernel part to light that red LED, since on Android it's only lit when charging, so this can be ignored.

Oh, that's fine. I just wanted to know if I "broke" the LED functionality somehow. You are absolutely right, nobody really needs that LED.

That's weird. I didn't see this on tablet. Usually this happens when it's waiting for ofono, but we don't have telephony.

I re-ran the upgrade instructions again. It seems like I might have skipped the "rm /lib/modules/3.10.20/*.ko" part the first time around. So sorry about that... :o

I planned to update it to 2.1.x, but still didn't do it. Will try to check it again.

It would so great if you could!!! Again, let me thank you so much for all the wonderful work you did here! It is truly appreciated!

[ferlanero]

I planned to update it to 2.1.x, but still didn't do it. Will try to check it again.

+1 for the 2.1.x update ;)

[tmi]

Here's a funny thing after the upgrade from the installer image to 2.0.5.6.

Instead of the normal "unlock" screen with the "> <" symbols I now just get a black screen with the rotating circle. :confused: At first I thought Lipstick hadn't started until I tried swiping.

Is there a method to remedy?

Funny, I had the same thing... silly me, I always thought it was due to some incompatibility with the hardware since I have the v820w V5 and never really paid any attention to it afterwards. Turns out I'd probably made some typo/mistake when originally upgrading as I just went through the upgrading steps and that seems to have fixed it.

EDIT: I had to install the tablet from scratch and it wasn't a typo after all as the problem reappeared. I believe zypper ref -f before running the long zypper install command again finally fixed it. YMMV
(I am not going to do everything all over again just to be sure, sorry)

Also, it took ages to get the WLAN working first. The best(/only?) way seemed to be from the prompt where the WLAN icon is presented and there is the text Turn WLAN on. I could never connect properly from Settings or Events View even though the password was 100% correct.
(After fighting this for way too long I am not sure anymore if the prompt appeared when trying to launch the Jolla Store with WLAN off but it just might've)

EDIT2: Ok, so I had to do it all over again :P
Due to that I made a github repo (https://github.com/tmikkonen/sailfish-onda-v820w).

(Yet again I had initial problems with the WLAN. Before the update I could connect best as I described earlier. Then after the update the only working way seemed to be from Settings.)

[tmi]

Any hope of a 2.1.3 update now that it's publicly available (https://blog.jolla.com/sailfish-os-2-1-3-now-available-early-access/)?
This fixes the WPA2 KRACK vulnerability (among other things) so it would be "nice to have" also on Onda tablets.

[TheKit]

Any hope of a 2.1.3 update now that it's publicly available (https://blog.jolla.com/sailfish-os-2-1-3-now-available-early-access/)?
This fixes the WPA2 KRACK vulnerability (among other things) so it would be "nice to have" also on Onda tablets.
I tried to update my tablet to 2.1.3.7 today. It mostly worked (after updating onda repo for 2.1.3.7 and manually installing some packages). Yet it seems to have broken Bluetooth and video recording with rear camera, need to investigate why.

[Amboss]

Yet it seems to have broken Bluetooth and video recording with rear camera, need to investigate why.
Probably because it's kind of broken even on official builds :(

[tmi]

BT and video recording are not that important to me (plus the tablet is for toying around) so I tried to adapt the 2.0.5.6 update instructions to 2.1.3.7 with "ssu re 2.1.3.7" and using "http://sfos.scanf.su/onda-v820w-v3/2.1.3.7" for adaptation-onda. Seems I didn't know what I was doing since "version --dup" couldn't find all the needed packages. I had nothing to lose so I even tried enabling adaptation0 & adaptation1 without luck.

Maybe an overkill, but in the end I re-ran the 2.0.5.6 update instructions and after rebooting the tablet was working fine as it was before my little experiment.

[smatkovi]

I tried to update my tablet to 2.1.3.7 today. It mostly worked (after updating onda repo for 2.1.3.7 and manually installing some packages). Yet it seems to have broken Bluetooth and video recording with rear camera, need to investigate why.

how did you do it, did you just override adaptation-onda or did you give one of them another name?
for me it says nothing provides pattern:jolla-hw-adaptation-hybris
after running version --dup

[TheKit]

how did you do it, did you just override adaptation-onda or did you give one of them another name?
for me it says nothing provides pattern:jolla-hw-adaptation-hybris
after running version --dup
I think I did the update by setting new version manually and updating through zypper. I will get to it again soon, I think the issues that were there can be fixed.

[smatkovi]

I think I did the update by setting new version manually and updating through zypper. I will get to it again soon, I think the issues that were there can be fixed.

I also updated through zypper, because version --DUP didn't work, because it asked for a pattern it didn't find, and the device didn't boot anymore. So I will have to get adaptor keyboard splitter and put sfos on a usbstick

[TheKit]

I also updated through zypper, because version --DUP didn't work, because it asked for a pattern it didn't find, and the device didn't boot anymore. So I will have to get adaptor keyboard splitter and put sfos on a usbstick
Does telnet connection work? You should be able to get logs or downgrade this way.

[smatkovi]

Does telnet connection work? You should be able to get logs or downgrade this way.

I think I messed something up, because when I downgrade to 2.0.5.7 I get the same error message. Oh and I can connect over WiFi I think, telnet I didn't manage to get working, also ssh over USB not. I an not at home until Monday so then I wool try again

[smatkovi]

Does telnet connection work? You should be able to get logs or downgrade this way.

i could "repair" it, but i couldn't resist trying to upgrade again. I did it like the instructions for 2.0.5.6, after upgrading to 2.0.5.6, except for instead of version --dup i did a zypper dup, because it didn't find the patterns, did it find the patterns for you? maybe it has something to do with that you have v3 and i have v5. in case you're interested i post dmesg output again^^

[smatkovi]

here's mine, as usual i just added the extension because of the filesize edit: experimental kernel with audio

i wonder if we can use windows drivers, but where to get them

[smatkovi]

does any telegramclient work for you?

[dubliner]

Is there any notion of a forthcoming upgrade of the present installation to 2.2.x?

I'm still using my Onda (SFOS 2.0.5.6) regularly, but find that a lot of software can no longer be upgraded or installed.

[smatkovi]

Is there any notion of a forthcoming upgrade of the present installation to 2.2.x?

I'm still using my Onda (SFOS 2.0.5.6) regularly, but find that a lot of software can no longer be upgraded or installed.

what software do you want to use?

[tmi]

Now that SFOS 3 is out I would love to use it with the white ambience on my white Onda tablet. I understand if the interest to craft an update for the device is slim - just mentioning there is still interest - especially after the Youyota tablet project apparently vaporized earlier this year.

[dubliner]

As aforementioned, I would love to have SFOS 3 running on the Onda tablet. Please please please... :-)

[dubliner]

Just wondering, am I the only one still (happily) using his Onda tablet? While luminosity could be better :rolleyes:, it's still a great device. If only I could get it updated to SFOS3... ;)

[ferlanero]

No, you are not the only one. I'm still use this tablet too. As you say, SF3 on this device would be fantastic !!

[smatkovi]

i use it too

[ferlanero]

It would be incredible to have a tablet full updated with Sailfish 3 running. I love how Sailfish performs on big screens!

[TheKit]

It would be incredible to have a tablet full updated with Sailfish 3 running. I love how Sailfish performs on big screens!
I will try to reuse https://github.com/g7/droid-compat-f5321 idea to make it more maintainable.

[ferlanero]

I will try to reuse https://github.com/g7/droid-compat-f5321 idea to make it more maintainable.

It sounds really, really great! I think all who have this tablet here, are using it due to its great performance still nowadays

[dubliner]

I will try to reuse https://github.com/g7/droid-compat-f5321 idea to make it more maintainable.

That's wonderful news!!! I am so eager to see the results! Thank you!!! :)

[dubliner]

Just last night I picked up my Onda again to do some reading. And I kept thinking how great it would be if I were able to install some more current packages.

May I just sheepishly ask how 3.0.2.8 is coming along for the Onda? ;) It would be wonderful to have my little tablet up to speed! :)

[TheKit]

Just last night I picked up my Onda again to do some reading. And I kept thinking how great it would be if I were able to install some more current packages.

May I just sheepishly ask how 3.0.2.8 is coming along for the Onda? ;) It would be wonderful to have my little tablet up to speed! :)
For the good news, I was able to upgrade mine to 3.0.2.8 with droid-compat packages (and it should be less hacky/easier to maintain) than previous approach.

Before trying, please back up the important data (or SailfishOS itself) in case reinstall would be needed. It is also better to have PC nearby which can be used for debugging via USB network connection if something goes wrong.

Here are the steps if you're on 2.1.3.7. I suspect it should work from 2.0.5.6 as well (then removing old -onda-v820w-v3 packages is not needed), but I didn't try it myself.

# First check if adaptation0 and adaptation1 repos are present and enabled, don't continue otherwise:
ssu lr

# Install back Jolla Tablet packages
zypper in pattern:jolla-configuration-tbj pattern:jolla-hw-adaptation-tbj

# Remove old modified packages (some will be already removed due to conflicts in previous step, do not reboot from this point)
zypper remove droid-bin-tbj-onda-v820w-v3 droid-config-tbj-onda-v820w-v3 droid-config-tbj-onda-v820w-v3-flashing droid-config-tbj-onda-v820w-v3-kickstart-configuration droid-config-tbj-onda-v820w-v3-patterns droid-config-tbj-onda-v820w-v3-policy-settings droid-config-tbj-onda-v820w-v3-preinit-plugin droid-config-tbj-onda-v820w-v3-pulseaudio-settings droid-config-tbj-onda-v820w-v3-sailfish droid-config-tbj-onda-v820w-v3-ssu-kickstarts droid-hal-tbj-onda-v820w-v3 droid-hal-tbj-onda-v820w-v3-detritus droid-hal-tbj-onda-v820w-v3-kernel droid-hal-tbj-onda-v820w-v3-kernel-modules droid-hal-tbj-onda-v820w-v3-tools

# Temporary add compat repo
ssu ar tmp-compat-v820w http://repo.merproject.org/obs/home:/TheKit:/compat-v820w/sailfish_latest_i486/
ssu ur
zypper ref tmp-compat-v820w
zypper in pattern:droid-compat-v820w
# It is now provided by droid-compat-droid-config package, so temporary entry can be removed
ssu rr tmp-compat-v820w

# Upgrade SailfishOS following all the stop releases:
ssu re 2.2.0.29
version --dup
reboot

ssu re 3.0.0.8
version --dup
reboot

ssu re 3.0.2.8
version --dup
reboot

[dubliner]

For the good news, I was able to upgrade mine to 3.0.2.8 with droid-compat packages

Thanks a million for that!!! I am really excited about this good news!!! :) I shall try this as soon as I find a liltle time (after all, I don't want to break anything only because I am rushing things).

Here are the steps if you're on 2.1.3.7. I suspect it should work from 2.0.5.6 as well

Will I need to ssu re 2.1.3.7 first? BTW, how did you get your tablet to version 2.1.3.7 in the first place? Maybe I could retrace those steps just to be sure!?

[tmi]

Will I need to ssu re 2.1.3.7 first?

My guess is no as it is not a stop release (https://jolla.zendesk.com/hc/en-us/articles/201836347#4). My guess might be wrong, though. I'll see what happens as soon as I have some time to try the upgrade.

EDIT: No luck with my 2.0.5.6 installation (adaptation0 & adaptation1 were present and enabled):
zypper in jolla-configuration-tbj jolla-hw-adaptation-tbj
first showed a popup complaining about my account settings, so I re-entered the Jolla Account credentials in Settings. Retrying the command didn't help, so I ran:
pkcon refresh

One more try, and I got the response:
'jolla-hw-adaptation-tbj' not found in package names. Trying capabilities. No provider of 'jolla-hw-adaptation-tbj' found.
'jolla-configuration-tbj' not found in package names. Trying capabilities. No provider of 'jolla-configuration-tbj' found.

I guess I'll have to try again when I have more time.

[dubliner]

Same here... I tried this and hit a bump right away. :( zypper in ... gave me this error:


[...]
'jolla-hw-adaptation-tbj' not found in package names. Trying capabilities.
No provider of 'jolla-hw-adaptation-tbj' found.
'jolla-configuration-tbj' not found in package names. Trying capabilities.
No provider of 'jolla-configuration-tbj' found.

Presumably, there is something wrong with the repositories on my Onda.


[root@Sailfish nemo]# ssu lr
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/releases/2.2.0.29/jolla-hw/adaptation-intel-tbj/i486/
- adaptation1 ... https://store-repository.jolla.com/releases/2.2.0.29/jolla-hw/adaptation-intel-tbj-dhd/i486/
- aliendalvik ... https://store-repository.jolla.com/releases/2.2.0.29/aliendalvik/tbj/
- apps ... https://releases.jolla.com/jolla-apps/2.2.0.29/i486/
- hotfixes ... https://releases.jolla.com/releases/2.2.0.29/hotfixes/i486/
- jolla ... https://releases.jolla.com/releases/2.2.0.29/jolla/i486/
- sailfish-eas ... https://store-repository.jolla.com/features/2.2.0.29/sailfish-eas/i486/?version=2.2.0.29
- xt9 ... https://store-repository.jolla.com/features/2.2.0.29/xt9/i486/

Enabled repositories (user):
- adaptation-onda ... http://sfos.scanf.su/onda-v820w-v3/
- adaptation0 ... https://store-repository.jolla.com/releases/2.2.0.29/jolla-hw/adaptation-intel-tbj/i486/
- adaptation1 ... https://store-repository.jolla.com/releases/2.2.0.29/jolla-hw/adaptation-intel-tbj-dhd/i486/
- mer-nielnielsen ... http://repo.merproject.org/obs/home:/nielnielsen/latest_i486
- openrepos-MartinK ... http://sailfish.openrepos.net/MartinK/personal/main
- openrepos-basil ... http://sailfish.openrepos.net/basil/personal/main
- openrepos-cnlpete ... http://sailfish.openrepos.net/cnlpete/personal/main
- openrepos-cy8aer ... http://sailfish.openrepos.net/cy8aer/personal/main
- openrepos-osetr ... http://sailfish.openrepos.net/osetr/personal/main
- openrepos-otsaloma ... http://sailfish.openrepos.net/otsaloma/personal/main
- openrepos-rinigus ... http://sailfish.openrepos.net/rinigus/personal/main
- openrepos-steffen_f ... http://sailfish.openrepos.net/steffen_f/personal/main
- openrepos-velox ... http://sailfish.openrepos.net/velox/personal/main
- store ... https://store-repository.jolla.com/tbj/i486/?version=2.2.0.29

Disabled repositories (global, might be overridden by user config):

Disabled repositories (user):
- home ... https://download.jollamobile.com/home:/honeybadger/latest_i486/
- openrepos-beidl ...

The version given as 2.2.0.29 bugs me, because AFAIK I got 2.0.5.6 installed and definitely never updated. :confused: I remember, though, the Jolla store mentioning there would be an update available. But I never tried to install it.


,---
| SailfishOS 2.0.5.6 (Haapajoki) (i486)
'---

What might be a prudent course of action now?

Another question: Apart from this problem, should I disable openrepos next time?

[dubliner]

P.S. Is there an easy (and still safe!!!) way to turn back the repositories to 2.0.5.6? Something like ssu re 2.0.5.6 maybe?

[dubliner]

Me again...

So, I tried
ssu re 2.0.5.6
pkcon refresh
zypper in jolla-configuration-tbj jolla-hw-adaptation-tbj
The result was the same: 'jolla-hw-adaptation-tbj' not found in package names etc.

Afterwards, I also re-tried the whole thing with ssu re 2.1.3.7 - still the same result.

So, I guess we'll need a hint where to find jolla-configuration-tbj and jolla-hw-adaptation-tbj. Any ideas?

[TheKit]

I made a mistake in the previous post. It should be:
zypper in pattern:jolla-configuration-tbj pattern:jolla-hw-adaptation-tbj

[dubliner]

Thank you so much for your help, @TheKit!

Alas, I managed to get myself into another mess. It seems like my Onda can't get into the store (after having removed a lot of rpms). In your list I am stuck at the first version --dup.

It seems like my Onda has forgotten it's Jolla credentials (agh!). Now the "Settings" in the GUI won't start, so I can't re-enter my username and password. Is there a way to enter the Jolla credentials on the command line?

Edit: I found ag-tool but don't know how to use it.

Any help will be appreciated!


[root@Sailfish nemo]# version --dup
REFRESHING CACHE AND DOWNLOADING PACKAGES
[0 %] [Download] droidmedia 0.20180406.1-1.7.3: [100 %]
Error: Installation aborted by user

Finished transaction (status=2, runtime=97889ms)
UPGRADE NOT COMPLETE - Retry 1 of 9
Waiting 1 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 8%


Refreshing: 75%
Message: adaptation0: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
adaptation1: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
aliendalvik: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
sailfish-eas: Store credentials not received. Failed to activate service 'com.jolla.jollastore': timed out
store: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
xt9: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[tmi]

Any help will be appreciated!

Have you tried running
pkcon refresh

It might not help but I exprienced some trouble with Jolla credentials earlier and that helped. I know it is an often suggested solution but then again in my own experience roughly 90% of any installation/upgrade problems I've come across have been resolved by it.
YMMV

EDIT: My bad, you actually have done that. Sorry, I wasn't paying enough attention to earlier messages.

[dubliner]

It worked!!! \o/

Before everyone stops reading: After the installation, I now only have four keyboard layouts: Emoji, English and what looks like two Chinese layouts.

How do I install more keyboard layouts?

Edit: Easily fixed, just run devel-su zypper in jolla-keyboard-layout-all

Back to the topic at hand...

Eventually, I had to reinstall SFOS with the installer from scratch (version 2.0.1.7). An intermediary attempt at first upgrading to 2.0.5.6 before proceeding failed again.

In the end, I used the installer once again and ran through the instructions (https://talk.maemo.org/showpost.php?p=1556234&postcount=177) in one go.

There was one curious thing that came up but didn't seem to matter in the end:

[root@Jolla nemo]# zypper in pattern:droid-compat-v820w
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: pattern:droid-compat-v820w-0.0.1-10.8.1.jolla.noarch requires droid-compat-v820w-droid-system, but this requirement cannot be provided
uninstallable providers: droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486[tmp-compat-v820w]
Solution 1: do not install pattern:droid-compat-v820w-0.0.1-10.8.1.jolla.noarch
Solution 2: break pattern:droid-compat-v820w-0.0.1-10.8.1.jolla.noarch by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 2
Resolving dependencies...

Also my tablet seemed to be a little confused about the versions it was running during the process. Alas, it did not interfere.

,---
| Sailfish OS 2.2.0.29 (Mouhijoki)
'---

[root@Sailfish nemo]# ssu re 3.0.0.8
Changing release from 3.0.0.8 to 3.0.0.8
Your device is now in release mode!

And a little later...

,---
| Sailfish OS 3.0.0.8 (Lemmenjoki)
'---

[root@Sailfish nemo]# ssu re 3.0.2.8
Changing release from 2.2.0.29 to 3.0.2.8
Your device is now in release mode!

@TheKit, THANK YOU SO VERY MUCH for all that work!!!

[tmi]

I also managed to upgrade, wohoo!

There were trouble at first with the repositories and/or credentials etc. and I didn't seem to be able to fix those so it was best to start all over from the start.

Updated also my repo (https://github.com/tmikkonen/sailfish-onda-v820w) if I need to do this again in the future.

Huge thanks once more to TheKit and also to dubliner for trailblazing & good info.

[dubliner]

Just wondering, does Bluetooth work for you? Nothing happens when I tap it.

dmesg: bcm_bt_lpm ... Error evaluating UART port number

Also, in AIDA64 all the sensors remain empty. I noticed this when I wasn't able to change the orientation. Didn't they use to work?

@tmi, you suggested installing jolla-settings-system-sideloading in your repo, however, I keep being asked for a password. How did you manage to do that?

Edit: Duh, I just needed to use zypper instead of pkcon. jolla-settings-system-sideloading is installed now! :)

[tmi]

Just wondering, does Bluetooth work for you? Nothing happens when I tap it.
BT tries to turn on but fails (shows briefly "on" via the quick buttons/top menu, keeps on flashing the dot via Settings). So no, it's not working... maybe it also needs a manually installed package? I haven't used BT with the tablet so I cannot say if it was working earlier or not.


Also, in AIDA64 all the sensors remain empty. I noticed this when I wasn't able to change the orientation. Didn't they use to work?

Accelometer, Compass, Orientation Sensor & Rotation Sensor give readings in Aida64 and I can turn the orientation to landscape just fine.

@tmi, you suggested installing jolla-settings-system-sideloading in your repo, however, I keep being asked for a password. How did you manage to do that?

Edit: Duh, I just needed to use zypper instead of pkcon. jolla-settings-system-sideloading is installed now! :)

Glad you got it installed with zypper! I don't ever remember being asked for a password when using pkcon.

FYI I'm running 3.0.3.8 Hossa as I've signed for EA releases, no developer updates/repos, though.

[dubliner]

BT tries to turn on but fails [...] maybe it also needs a manually installed package? I haven't used BT with the tablet so I cannot say if it was working earlier or not.

To be quite honest, I don't remember with any certainty whether I used to have BT working on the tablet. I always thought so, but who knows... Bluetooth shows up as version 3.0 on Aida64. So, I really wonder what might be missing...

Accelometer, Compass, Orientation Sensor & Rotation Sensor give readings in Aida64 and I can turn the orientation to landscape just fine.

That's interested. I kept rebooting my Onda for several times, but no luck. All of the sensors are left blank on Aida64. sigh... :( Might your different outcome have something to do with your upgrade to Hossa? BTW, I am looking forward to doing that myself. Yet, I will wait for the release (can't be too much longer, can it? ;) ).

[tmi]

That's interested. I kept rebooting my Onda for several times, but no luck. All of the sensors are left blank on Aida64. sigh... :( Might your different outcome have something to do with your upgrade to Hossa? BTW, I am looking forward to doing that myself. Yet, I will wait for the release (can't be too much longer, can it? ;) ).

Your guess is as good as mine regarding Hossa and the sensors. I take it landscape isn't working for you? I think it was already working for me on 3.0.0.8 but I cannot be sure as I repeated the install & upgrade process on the tablet 2-3 times while trying different things until I was happy with it.

Also, for some reason I've always had hard time connecting to wifi for the first time (after that it connects automatically just fine) on the initial install. I'm not claiming this has anything to do with the sensors just that things might be a little hit&miss with these (cheap) tablets.

I know it's a bit of a pain but you could always try to re-install your tablet if all else fails or Hossa doesn't help either.

[dubliner]

While I am waiting for version --dup to entice me with a whole new version of SFOS (yay \o/ ), I started thinking that, maybe, that one error I encountered during the initial installation might be the cause for the non-functional sensors:

[root@Jolla nemo]# zypper in pattern:droid-compat-v820w
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: pattern:droid-compat-v820w-0.0.1-10.8.1.jolla.noarch requires droid-compat-v820w-droid-system, but this requirement cannot be provided
uninstallable providers: droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486[tmp-compat-v820w]

Is there any way I could (should?) install that package droid-compat-v820w-droid-system now?

Edit: Running zypper in droid-compat-v820w-droid-system fixed the sensors issue!!! \o/ Unfortunately, no change with BT, though.


Also, for some reason I've always had hard time connecting to wifi for the first time (after that it connects automatically just fine) on the initial install.

I've known this problem only too well! Actually, for me it's been a problem with every SFOS device I use (Nexus5, Onyx and the Onda). Might this be a general connman issue? Has anyone else encountered that and maybe found a solution?

[dubliner]

Edit: Running zypper in droid-compat-v820w-droid-system fixed the sensors issue!!! \o/ Unfortunately, no change with BT, though

When I went over the output again, there is one thing that stood out:

Problem: nothing provides droid-system-tbj needed by droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486

Maybe this is the key to the missing Bluetooth functionality. Thus, there are two questions on my mind?

1) Where can I get this package from? droid-system-tbj
2) Is it safe to install it now (i.e. "last")?

[ferlanero]

It worked!!! \o/

Before everyone stops reading: After the installation, I now only have four keyboard layouts: Emoji, English and what looks like two Chinese layouts.

How do I install more keyboard layouts?

Edit: Easily fixed, just run devel-su zypper in jolla-keyboard-layout-all

Unfortunately not working for me:

[root@Sailfish nemo]# zypper in jolla-keyboard-layout-all
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 requires jolla-keyboard-layout-western, but this requirement cannot be provided
not installable providers: jolla-keyboard-layout-western-0.7.2-1.10.4.jolla.i486[jolla]
Solution 1: Following actions will be done:
downgrade of jolla-keyboard-0.7.3-1.11.1.jolla.i486 to jolla-keyboard-0.7.2-1.10.4.jolla.i486
downgrade of jolla-keyboard-hwr-0.7.3-1.11.1.jolla.i486 to jolla-keyboard-hwr-0.7.2-1.10.4.jolla.i486
Solution 2: do not install jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486
Solution 3: break jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c): 3
Resolving dependencies...
Resolving package dependencies...

The following NEW package is going to be installed:
jolla-keyboard-layout-all

1 new package to install.
Overall download size: 31.2 KiB. Already cached: 0 B. No additional space will be used or freed after the operation.
Continue? [y/n/...? shows all options] (y): y
Retrieving package jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 (1/1), 31.2 KiB ( 0 B unpacked)
Retrieving: jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486.rpm .................................................. .[done (38 B/s)]
Checking for file conflicts: .................................................. ...............................................[done]
(1/1) Installing: jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 .................................................. ........[done]
Additional rpm output:
warning: /home/.zypp-cache/packages/jolla/non-oss/i486/jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486.rpm: Header V3 DSA/SHA1 Signature, key ID f2633ee0: NOKEY


The package install itself but I can't see more keyboards layouts in settings to choose :( Do you have any ideas?

Edit: I only need to install Spanish layout in addition.

[ferlanero]

Edit: Running zypper in droid-compat-v820w-droid-system fixed the sensors issue!!! \o/ Unfortunately, no change with BT, though.

Not working for me neither:

[root@Sailfish nemo]# zypper in droid-compat-v820w-droid-system
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides droid-system-tbj needed by droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486
Solution 1: do not install droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486
Solution 2: break droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 2
Resolving dependencies...
Resolving package dependencies...

The following 4 NEW packages are going to be installed:
droid-compat-v820w-droid-system libpython3_7m1_0 python3-base rpm-divert

4 new packages to install.
Overall download size: 2.9 MiB. Already cached: 9.8 MiB. After the operation, additional 56.6 MiB will be used.
Continue? [y/n/...? shows all options] (y): y
In cache libpython3_7m1_0-3.7.2+git1-1.3.2.jolla.i486.rpm (1/4), 838.9 KiB ( 2.6 MiB unpacked)
In cache python3-base-3.7.2+git1-1.3.2.jolla.i486.rpm (2/4), 9.0 MiB ( 39.1 MiB unpacked)
Retrieving package rpm-divert-0.0.5-1.2.1.jolla.noarch (3/4), 31.1 KiB ( 76.4 KiB unpacked)
Retrieving: rpm-divert-0.0.5-1.2.1.jolla.noarch.rpm .................................................. ...................[not found]
File './noarch/rpm-divert-0.0.5-1.2.1.jolla.noarch.rpm' not found on medium 'http://repo.merproject.org/obs/home:/TheKit:/compat-v820w/sailfish_latest_i486/'
Abort, retry, ignore? [a/r/i/...? shows all options] (a): i
Warning: You have chosen to ignore a problem with download or installation of a package which might lead to broken dependencies of other packages. It is recommended to run 'zypper verify' after the operation has finished.
Retrieving package droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486
(4/4), 2.9 MiB ( 14.9 MiB unpacked)
Retrieving: droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486.rpm ...................[not found]
File './i486/droid-compat-v820w-droid-system-0.0.1+master.20190420220535.ed0e0f4-1.13.1.jolla.i486.rpm' not found on medium 'http://repo.merproject.org/obs/home:/TheKit:/compat-v820w/sailfish_latest_i486/'
Abort, retry, ignore? [a/r/i/...? shows all options] (a): i
Warning: You have chosen to ignore a problem with download or installation of a package which might lead to broken dependencies of other packages. It is recommended to run 'zypper verify' after the operation has finished.
Installation has completed with error.



Choosing second option at last does nothing.

Any ideas, please?

[tmi]

Have you tried refreshing
zypper ref -f
What happens if you choose 1 for downgrading with the keyboard layouts?

EDIT: There is also the package jolla-keyboard-layout-western you could try to install

[dubliner]

Problem: jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 requires jolla-keyboard-layout-western, but this requirement cannot be provided
not installable providers: jolla-keyboard-layout-western-0.7.2-1.10.4.jolla.i486[jolla]

I'd just like to confirm that for me this file (with a few more) was installed automatically.

Could you check your repositories? Mine look like this, although the 3.0.2.8 baffles me:


,---
| Sailfish OS 3.0.3.9 (Hossa)
'---
[nemo@Sailfish ~]$ ssu lr
WARNING: ssu.ini does not seem to be writable. Setting values might not work.
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/releases/3.0.2.8/jolla-hw/adaptation-intel-tbj/i486/
- adaptation1 ... https://store-repository.jolla.com/releases/3.0.2.8/jolla-hw/adaptation-intel-tbj-dhd/i486/
- apps ... https://releases.jolla.com/jolla-apps/3.0.2.8/i486/
- compat-v820w ... http://repo.merproject.org/obs/home:/TheKit:/compat-v820w/sailfish_latest_i486/
- hotfixes ... https://releases.jolla.com/releases/3.0.2.8/hotfixes/i486/
- jolla ... https://releases.jolla.com/releases/3.0.2.8/jolla/i486/
- sailfish-eas ... https://store-repository.jolla.com/features/3.0.2.8/sailfish-eas/i486/


You could also try that magic devel-su pkcon refresh which seems to solve a lot of mysterious problems.

Okay, and now I'll look into why my repos haven't upgraded to 3.0.3.9... :rolleyes:

P.S. Anyway, I ran ssu re 3.0.3.9 ; version --dup again and all the repos are now showing the correct version. No idea how that happened. Guess my Onda must be time travelling when I'm not looking. :cool:

P.P.S. Still can't find the package my Onda had been complaining about earlier.

$ devel-su zypper in droid-system-tbj
Password:
Loading repository data...
Reading installed packages...
'droid-system-tbj' not found in package names. Trying capabilities.
No provider of 'droid-system-tbj' found.
Resolving package dependencies...

Nothing to do.

Where can I get droid-system-tbj from? And do I actually need to install it? Might this be the reason for the lack of Bluetooth functionality?

[ferlanero]

Have you tried refreshing
zypper ref -f
What happens if you choose 1 for downgrading with the keyboard layouts?

EDIT: There is also the package jolla-keyboard-layout-western you could try to install

Sadly it doesn't help. I still can't install any other keyboard :(

[ferlanero]

I'd just like to confirm that for me this file (with a few more) installed automatically.

Could you check your repositories? Mine look like this, although the 3.0.2.8 baffles me:

Ok, same here. My tablet is on 3.0.2.8 repositories:

[ferlanero@ferlanero-imac ~]$ ssh nemo@192.168.1.13
nemo@192.168.1.13's password:
Last login: Sat May 11 19:05:46 2019 from 192.168.1.102
,---
| Sailfish OS 3.0.3.9 (Hossa)
'---
[nemo@Sailfish ~]$ ssu lr
WARNING: ssu.ini does not seem to be writable. Setting values might not work.
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/releases/3.0.2.8/jolla-hw/adaptation-intel-tbj/i486/
- adaptation1 ... https://store-repository.jolla.com/releases/3.0.2.8/jolla-hw/adaptation-intel-tbj-dhd/i486/
- aliendalvik ... https://store-repository.jolla.com/releases/3.0.2.8/aliendalvik/tbj/
- apps ... https://releases.jolla.com/jolla-apps/3.0.2.8/i486/
- compat-v820w ... http://repo.merproject.org/obs/home:/TheKit:/compat-v820w/sailfish_latest_i486/
- hotfixes ... https://releases.jolla.com/releases/3.0.2.8/hotfixes/i486/
- jolla ... https://releases.jolla.com/releases/3.0.2.8/jolla/i486/
- sailfish-eas ... https://store-repository.jolla.com/features/3.0.2.8/sailfish-eas/i486/
- xt9 ... https://store-repository.jolla.com/features/3.0.2.8/xt9/i486/

Enabled repositories (user):
- openrepos-Mister_Magister ... https://sailfish.openrepos.net/Mister_Magister/personal/main
- openrepos-nodevel ... https://sailfish.openrepos.net/nodevel/personal/main
- openrepos-osetr ... https://sailfish.openrepos.net/osetr/personal/main
- openrepos-thebootroo ... https://sailfish.openrepos.net/thebootroo/personal/main
- store ... https://store-repository.jolla.com/tbj/i486/?version=3.0.2.8

Disabled repositories (global, might be overridden by user config):

Disabled repositories (user):
- home ... https://download.jollamobile.com/home:/honeybadger/latest_i486/
- mer-tools ...
[nemo@Sailfish ~]$

[ferlanero]

Ok, after doing "ssu re 3.0.3.9" and "version --dup" by second time, alot of package seems that was missing and install flawlessly. No problem. Now it seems that we are in real 3.0.3.9, because doing by third time "ssu re 3.0.3.9" and "version --dup" terminal says: "NO UPDATES FOUND. Try again later."

But problem with keyboard languages persist, but now in a different way:

[root@Sailfish nemo]# zypper in jolla-keyboard-layout-all
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 requires jolla-keyboard-layout-western, but this requirement cannot be provided
not installable providers: jolla-keyboard-layout-western-0.7.2-1.10.4.jolla.i486[jolla]
Solution 1: Following actions will be done:
downgrade of jolla-keyboard-0.7.3-1.11.1.jolla.i486 to jolla-keyboard-0.7.2-1.10.4.jolla.i486
downgrade of jolla-keyboard-hwr-0.7.3-1.11.1.jolla.i486 to jolla-keyboard-hwr-0.7.2-1.10.4.jolla.i486
Solution 2: do not install jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486
Solution 3: break jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c): 3
Resolving dependencies...
Resolving package dependencies...

The following NEW package is going to be installed:
jolla-keyboard-layout-all

1 new package to install.
Overall download size: 31.2 KiB. Already cached: 0 B. No additional space will be used or freed after the operation.
Continue? [y/n/...? shows all options] (y): y
Retrieving package jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486 (1/1), 31.2 KiB ( 0 B unpacked)
Retrieving: jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486.rpm .................................................. .....[not found]
File './non-oss/i486/jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486.rpm' not found on medium 'https://releases.jolla.com/releases/3.0.3.9/jolla/i486/'
Abort, retry, ignore? [a/r/i/...? shows all options] (a): a
Problem occurred during or after installation or removal of packages:
Installation aborted by user
Please see the above error message for a hint.
[root@Sailfish nemo]#

Now system can't find "jolla-keyboard-layout-all-0.7.2-1.10.4.jolla.i486.rpm" package anymore, what leads me to think about the posibility of... "pkcon refresh" and...

Bingo!

[root@Sailfish nemo]# zypper in jolla-keyboard-layout-all
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 7 NEW packages are going to be installed:
jolla-keyboard-layout-all jolla-keyboard-layout-chinese jolla-keyboard-layout-indian jolla-keyboard-layout-kazakh
jolla-keyboard-layout-russian jolla-keyboard-layout-tatar jolla-keyboard-layout-western

7 new packages to install.
Overall download size: 241.5 KiB. Already cached: 0 B. After the operation, additional 174.9 KiB will be used.
Continue? [y/n/...? shows all options] (y):

That's the problem. You will need to run twice "ssu re 3.0.3.9" and "version --dup" then "pkcon refresh" and you'll be fine to install all the package you need in 3.0.3.9 Hossa

[ferlanero]

Unfortunately still:

[root@Sailfish nemo]# zypper in droid-systemd-tbj
Loading repository data...
Reading installed packages...
'droid-systemd-tbj' not found in package names. Trying capabilities.
No provider of 'droid-systemd-tbj' found.
Resolving package dependencies...

Nothing to do.
[root@Sailfish nemo]#

[tmi]

I installed bluez5 to the tablet as it had bluez4. No change.
Then I noticed the package droid-config-tbj-bluez5 isn't installed even though droid-config-tbj-bluez4 was earlier.

I tried to install it but unfortunately the package conflicts with bluez-configs provided by droid-config-tbj-onda-v820w-v3-1-2.i486 and cannot be installed.

If I try removing bluez-configs first I get a warning that I will end up with a broken system which is something I don't want to try now since BT isn't essential for me.

(Basically just shots in the dark, but thought I'd share anyway)

[dubliner]

That's the problem. You will need to run twice "ssu re 3.0.3.9" and "version --dup" then "pkcon refresh" and you'll be fine to install all the package you need in 3.0.3.9 Hossa

If your outcome is anything like mine, you will need to install the sensors once again: zypper in droid-compat-v820w-droid-system

I installed bluez5 to the tablet as it had bluez4. No change.

I don't think that's a good idea. Some other devices are also still running Bluez4 for good reasons.

Presumably, only TheKit will be able to help us with this one.

[tmi]

I don't think that's a good idea. Some other devices are also still running Bluez4 for good reasons.

Sure, but luckily it was easy enough to change back to bluez4.

Regarding BT I saw this (http://talk.maemo.org/showpost.php?p=1538645&postcount=154) while going back the thread. So BT was probably working in 2.0.5.6 and broke after that.

[dubliner]

So BT was probably working in 2.0.5.6 and broke after that.

TheKit actually mentioned it was still working for him. I still suspect the missing package droid-systemd-tbj to be a relevant factor in this.

Something completely different: Does your Onda actually support GPS? Mine claims to support it, but when I use GPSInfo it never even "sees" any satellites. Contrary to this the Nexus5 saw dozens within seconds. So, either the Onda "lies" about its GPS capabilities or it's simply broken in my device.

[tmi]

Does your Onda actually support GPS?

To my knowledge the Onda doesn't support GPS. Here's one review (https://soundreview.org/tech/onda-v820w-windowsandroid-tablet-review/) that claims the same. Maybe there's still some use for location services if you switch High-accuracy positioning to use also online services?

BTW: When booting the tablet do you have the black screen and circle (http://talk.maemo.org/showpost.php?p=1533339&postcount=149)? I remember getting rid of it on some 2.0.5.6 reinstall but now it seems to be back for me on SFOS 3.

As such, not a big issue... and I don't think removing ofono is the right choice, either :)

[dubliner]

When booting the tablet do you have the black screen and circle (http://talk.maemo.org/showpost.php?p=1533339&postcount=149)? I remember getting rid of it on some 2.0.5.6 reinstall but now it seems to be back for me on SFOS 3.

Last time (#150 (http://talk.maemo.org/showpost.php?p=1533352&postcount=150)) I faced this problem, this is what I did:

I re-ran the upgrade instructions again. It seems like I might have skipped the "rm /lib/modules/3.10.20/*.ko" part the first time around. So sorry about that...

This time I did not encounter this situation, even though I installed from scratch using the automatic installer (https://talk.maemo.org/showpost.php?p=1505017&postcount=1) and just kept upgrading according to TheKit's instructions (https://talk.maemo.org/showpost.php?p=1556234&postcount=177) after that. Alas, my Onda is still pining for the missing package droid-systemd-tbj.

[tmi]

What a can of worms... :)

While trying to get rid of the blank screen I decided to reinstall the tablet from the scratch. Previously, I had skipped removing old modified packages as the instructions mention "...removing old -onda-v820w-v3 packages is not needed...". Now I did remove them.

All went well and the blank screen was gone after the 2.2.0.29 upgrade, also after the upgrade to 3.0.0.8. Then I wanted to speed up and upgraded straight to 3.0.3.9. While rebooting the tablet it didn't go past the ANDROID text... bummer.

Second try from the scratch, same result.

Third try from the scratch and but this time upgrading 3.0.0.8. -> 3.0.2.8. Same result yet again, sheesh!

At this point, I decided not to mind the blank screen and started yet another reinstall without removing the old packages hoping to finally upgrade to 3.0.3.9. This time the tablet booted all the way through after the upgrade to 3.0.2.8 but for some reason it claimed to be already on 3.0.3.9! On top of this, I had some trouble installing the missing keyboard layouts etc. but succeeded finally. I re-ran the 3.0.3.9 upgrade once more and guess what, the tablet didn't boot anymore!

Fifth time's the charm, so I started from the scratch once more. Now I installed the missing layouts + sideloading after the 2.2.0.29 upgrade before upgrading to 3.0.0.8 and everything went smoothly. Then I upgraded 3.0.0.8 -> 3.0.3.9 and finally I have an up to date working tablet again and yes, with the blank screen & circle on boot!

Well, at least I'm quite familiar with the process now and can at least get the WLAN to connect pretty quickly (the trick was to keep it off initially and only turn it on when adding a new account... that way it connects 80-90% of the time on first try)

I'm not hoping to reinstall the Onda anytime soon!

[dubliner]

Phew, what a can of worms indeed!!! It really makes you wonder why the outcomes are so extremely different each time one installs or upgrades. Presumably it boils down to some repos failing (in different ways). Either access is blocked ("adaptation0: Store credentials not received.") or the list of available files is incomplete ("...requires droid-compat-v820w-droid-system, but this requirement cannot be provided" -> yet, zypper in droid-compat-v820w-droid-system worked like a charm a few minutes later and all the sensors returned). And there is still that issue of the missing package droid-systemd-tbj (I keep mentioning this hoping someone might actually have an idea where to find it). So, it all boils down to infrastructure problems, doesn't it?

About your try #5: Actually, I didn't do any of this - like no missing layouts or sideloading. Only after having reached 3.0.3.9 I took care of these things. Does this mean you actually got the missing package installed and Bluetooth is working?

At the same time, I cannot help but wonder how time consuming and tedious all the porting must be for TheKit. I am so grateful he's doing that for us! :-)

[TheKit]

And there is still that issue of the missing package droid-systemd-tbj (I keep mentioning this hoping someone might actually have an idea where to find it). So, it all boils down to infrastructure problems, doesn't it.
Now that you wrote it in large red, I see the the extra "d" at the end. That's my typo, sorry for this, can be safely ignored until fixed one is on OBS.

[tmi]

It really makes you wonder why the outcomes are so extremely different each time one installs or upgrades.

I also wondered about this. The downloading process does a few retries (1 of 9, 2 of 9...) and sometimes the problems resolve, sometimes they do not. Also the wifi connection isn't necessarily the most stable one (at least on SFOS 2 where I had a couple of frustrating dropouts). I think I encountered less problems with "store credentials" etc. when the Sailfish OS check for updates was set to Manual instead of Automatic but maybe that's just a coincidence.

One factor might also be my V5 tablet itself but I've understood the V3 has its quirks, too.

I recall the "mystery" package to be named droid-system-tbj (not ...systemd...) but no importance since it cannot be found nonetheless.

EDIT: Ah...

Now that you wrote it in large red, I see the the extra "d" at the end. That's my typo, sorry for this, can be safely ignored until fixed one is on OBS.

I was slow :)


About your try #5: Actually, I didn't do any of this - like no missing layouts or sideloading. Only after having reached 3.0.3.9 I took care of these things. Does this mean you actually got the missing package installed and Bluetooth is working?

Sorry, BT isn't working.
When I originally managed to upgrade the tablet from 2.0.5.6 I only fixed the layouts on 3.0.3.8 (without a hitch). However now for some reason on try #4 I had to downgrade maybe 3-4 packages and install a couple of others and I lost track what was really happening so no wonder the tablet failed to boot afterwards... (sure, there was also the OS version inconsistency). On try #5 I decided to install the missing packages right after they'd gone missing which seemed like the right choice.


...how time consuming and tedious all the porting must be for TheKit. I am so grateful he's doing that for us! :-)

Absolutely! I would've understood perfectly if he'd just call it quits on SFOS3 & Onda but instead it looks like he managed to provide an easily upgradable solution *knocks on wood*.

[dubliner]

Now that you wrote it in large red,

Erm, well, I did feel a little silly when I did it, but I am delighted to see it actually worked. ;)

I see the the extra "d" at the end. That's my typo, sorry for this, can be safely ignored until fixed one is on OBS.

Great, so I can just relax about that. Thanks so much for all your help!!! :)

[ferlanero]

Now that you wrote it in large red, I see the the extra "d" at the end. That's my typo, sorry for this, can be safely ignored until fixed one is on OBS.

So, you say that we can just have Bluetooth working again any time soon? :)

[dubliner]

Just a quick one. My Onda notified me about the official 3.0.3.10 upgrade being available. Has anyone tried this? Is it safe?

[tmi]

Just a quick one. My Onda notified me about the official 3.0.3.10 upgrade being available. Has anyone tried this? Is it safe?

1MB trivial upgrade that probably did hardly more than updated the OS version :)

Things might be different with Alien Dalvik installed, though.

[dubliner]

1MB trivial upgrade that probably did hardly more than updated the OS version :)

Things might be different with Alien Dalvik installed, though.

Thanks for your quick response. In fact, I don't need to worry about Alien Dalvik as I don't have it installed (if I wanted Android apps, I figure I could just run Android, which I really don't like - if that even makes sense ;) ).

So, I gather everybody but me has already upgraded their Ondas to 3.0.3.10 and has been sailfishing happily ever since?

[ferlanero]

At the end, someone has tried the 3.0.3.10 update? Is it safe to aply or it just brokes everything in our beloved Onda V820W? :)

[dubliner]

I haven't... Yes, I know I'm a chicken... :)

[tmi]

Just a quick heads up:

Yes, Onda can be upgraded to 3.1.0.11 (Seitseminen).
GUI may or may not work, I used the Terminal.

No, BT isn't working.

[ferlanero]

Just a quick heads up:

Yes, Onda can be upgraded to 3.1.0.11 (Seitseminen).
GUI may or may not work, I used the Terminal.

No, BT isn't working.

Do you have test it? Is it safe to update to 3.1.0.11 via terminal?

devel-su

ssu release 3.1.0.11

version --dup

[tmi]

Do you have test it? Is it safe to update to 3.1.0.11 via terminal?

I don't really know what people mean regarding a "safe" upgrade. What I can tell is:
- How did you upgrade? Using terminal
- Does the GUI upgrade work? I don't know (I have tried it on some previous upgrade without trouble, though)
- Did the upgrade complete with no errors? Yes
- After reboot does the system SEEM to be working as it did before? Yes
- Have you noticed anything 'weird'? Possibly some faster power drain (but even if true it isn't most likely device specific).

As I understood TheKit's previous post (https://talk.maemo.org/showpost.php?p=1551733&postcount=173) there shouldn't really be need to wonder on every possible SFOS3 upgrade will it work on Onda. Then again, I might be wrong.

Also, even if I was correct now the situation may well change in the future, so don't take my word for any guarantee.


devel-su
ssu release 3.1.0.11
version --dup

Yes, that's what I did.
The tablet was charging and I enabled the display option to prevent display from blanking while charging the battery like I usually do with Onda upgrades.

[ferlanero]

Thanks for the answer! I'm going to try! :D

[ferlanero]

Well I just have upgraded my Onda V820W to SailfishOS 3.1.0.11 and everything went like a charm! Great!!

[ferlanero]

After updating Onda V820W V3 to SailfishOs 3.1.0.11 there is only an issue: There is no sound system wide, but you can fix it by forcing installing droid-compact-v820w-droid-system by:

devel-su zypper in droid-compact-v820w-droid-system

[tmi]

Good to know, thanks! I have V5 so there is no sound either way... (or at least until SFOS uses a newer kernel that supports sound on V5).

[ferlanero]

(or at least until SFOS uses a newer kernel that supports sound on V5).

It will occur anytime soon on the Onda port? I doubt it... :/

[tmi]

It will occur anytime soon on the Onda port? I doubt it... :/

I don't think it has nothing to do with Onda specifically. I mean SFOS cannot stay on 3.10 Kernel forever..? Whatever the case, I dont't need the audio for anything necessarily so if nothing happens, I don't mind.

[monkeyisland]

Hi there i did the instructions.
But i got a grub error that rus. language is not available any hints;)

[tmi]

Hi there i did the instructions.
But i got a grub error that rus. language is not available any hints;)

#32 (https://talk.maemo.org/showpost.php?p=1513778&postcount=32)
You need to comment it out.

[monkeyisland]

Okay i did that script fails :
no bzip image found..
Sorry for the short info

[tmi]

Make sure the USB stick is labelled "USB".

[monkeyisland]

usb stick how can i boot ? Key kombination?
With micro SD card inserted. i plugged a usb keyboard in the micro usb port.
i formatted microsd card to Fat32 with one partition.
i unzipped the file:
so i got :



;) it is right ?

[tmi]

I have no idea if the tablet can be booted from the microSD or not. Using a FAT32 formatted USB stick the label should be USB. Just unzip the files to the root same as you did with the microSD already (or copy them from the microSD, should make no difference).

You also need a (powered) USB hub and USB keyboard&mouse.
Just press ESC while booting, select Boot Manager (here you need the mouse) and finally select the USB stick (with the keyboard, if I recall correctly).

Skim/read through this Onda thread, all the information you need should be mentioned along the way.

[monkeyisland]

So special thanks it is working.
Anybody knows to get a spare battery for this tablet ?

btw: i test to upgrade to 2.2.0.29 it failed. :o
i will read the thread for a solution.;)

edit:

https://github.com/tmikkonen/sailfish-onda-v820w

works great ...

other issue on filemanager only 10 gb will shown i got an 32 GB tablet any solution ? :p

[tmi]

other issue on filemanager only 10 gb will shown i got an 32 GB tablet any solution ? :p

I don't know if it's the easiest but create a bootable Linux USB stick (Ubuntu, Linux Mint etc.), boot the tablet from it, start GParted and resize the tablet's partition... you'll need the USB hub + keyboard & mouse again.

[monkeyisland]

@:tmi need a 32 bis efi ? or 64 bit

so download a 64 bit linux mint iso ?
an copy to usbstick ?

[tmi]

@:tmi need a 32 bis efi ? or 64 bit

This (https://medium.com/@tomac/installing-ubuntu-mint-linux-on-onda-820w-tablet-727747a376b#.efqtdvkgs) might help.
EDIT: or this (http://techcat.ca/threads/onda-v975w-tablet-guide-installing-ubuntu-mint-linux-on-intel-atom-bay-trail-tablet.8/).


so download a 64 bit linux mint iso ?
an copy to usbstick ?

You probably need to use dd or UNetbootin or similar to create a bootable USB from the ISO image. (I think there was even some USB creator program included if you boot the Linux Mint "LiveCD" on a PC)

[monkeyisland]

So finally .. i managed it... :D:D

I downloaded following iso https://sourceforge.net/projects/gparted/

With AcetoneISO downloaded from Softwareshop under Linux Mint 18.3 on MacMini i decompressed the iso to the usb stick.

The i take my USB Hub and bootet from the Stick.
I used default settings.

After a while the Debian Desktop was shown.
So i expanded the Sailfish Partition to the maximum.
Now i had 24,7 GB free. :D

[ferlanero]

So finally .. i managed it... :D:D

I downloaded following iso https://sourceforge.net/projects/gparted/

With AcetoneISO downloaded from Softwareshop under Linux Mint 18.3 on MacMini i decompressed the iso to the usb stick.

The i take my USB Hub and bootet from the Stick.
I used default settings.

After a while the Debian Desktop was shown.
So i expanded the Sailfish Partition to the maximum.
Now i had 24,7 GB free. :D

Which options have you used? Because I can't up the graphical session :/

[ferlanero]

Ok. To make the proper Gparted USB live bootable on Onda V820W is much better to follow the manual method to get the GUI up properly: https://gparted.org/liveusb.php#linux-method-b

[ferlanero]

Here you have some pics of the whole process. Hope you enjoy it:

[monkeyisland]

Hi there is there any chance to get audio working my tablet is a v4?:D

Another problem my tablet says always is loading but there is no charger in it.
Funny thing when i connect a micro usb to usb Adapter for USB_Sticks. without a stick: the charging symbol is gone :o

[monkeyisland]

very strange i did the same as before but now i am end in a grub minimal bash.
My Stick is Fat32 formatted.
Can you send me you contents of your usb stick ?

edit:
managed it. it was the false bootia32.efi file .:D

[dubliner]

While trying to update to version 3.1.x, I foolishly typed ssu release 3.1.0.12 instead of ssu release 3.1.0.11. Only later I noticed my mistake. My attempt at downgrading to 3.1.0.11 (I know this is not recommended) left me with no audio.

Is there an easy way to restore audio (i.e. re-installing some rpm)?

[ferlanero]

Ok. To make the proper Gparted USB live bootable on Onda V820W is much better to follow the manual method to get the GUI up properly: https://gparted.org/liveusb.php#linux-method-b

It's really easy:

devel-su zypper in droid-compat-v820w-droid-system

[ferlanero]

Onda V820W V3 successfully updated to Sailfish 3.2.0.12 Torronsuo throughout GUI. No issues found, but don't forget to make a:

devel-su pkcon refresh

after update ;)

[dubliner]

Thanks for the info, ferlanero. So, I tried the same thing here. The upgrade itself worked. However, I am left with no sound again.

This did not work, either:
,---
| Sailfish OS 3.2.0.12 (Torronsuo)
'---
[nemo@Sailfish ~]$ devel-su zypper in droid-compact-v820w-droid-system
Password:
Loading repository data...
Reading installed packages...
'droid-compact-v820w-droid-system' not found in package names. Trying capabilities.
No provider of 'droid-compact-v820w-droid-system' found.
Resolving package dependencies...

Nothing to do.

How did you fix this?

[ferlanero]

Thanks for the info, ferlanero. So, I tried the same thing here. The upgrade itself worked. However, I am left with no sound again.

This did not work, either:
,---
| Sailfish OS 3.2.0.12 (Torronsuo)
'---
[nemo@Sailfish ~]$ devel-su zypper in droid-compact-v820w-droid-system
Password:
Loading repository data...
Reading installed packages...
'droid-compact-v820w-droid-system' not found in package names. Trying capabilities.
No provider of 'droid-compact-v820w-droid-system' found.
Resolving package dependencies...

Nothing to do.

How did you fix this?

devel-su pkcon refresh

devel-su zypper in droid-compat-v820w-droid-system

And everything is working again :)

[dubliner]

[...] And everything is working again :)

I am afraid it does not work for me. :confused: Even after a pkcon refresh I'm still getting the same error message (No provider of 'droid-compact-v820w-droid-system' found.).

Which repositories are active on your Onda?

[root@Sailfish nemo]# ssu lr
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/releases/3.2.0.12/jolla-hw/adaptation-intel-tbj/i486/
- adaptation1 ... https://store-repository.jolla.com/releases/3.2.0.12/jolla-hw/adaptation-intel-tbj-dhd/i486/
- apps ... https://releases.jolla.com/jolla-apps/3.2.0.12/i486/
- compat-v820w ... http://repo.merproject.org/obs/home:/TheKit:/compat-v820w/sailfish_latest_i486/
- hotfixes ... https://releases.jolla.com/releases/3.2.0.12/hotfixes/i486/
- jolla ... https://releases.jolla.com/releases/3.2.0.12/jolla/i486/
- sailfish-eas ... https://store-repository.jolla.com/features/3.2.0.12/sailfish-eas/i486/

Enabled repositories (user):
- store ... https://store-repository.jolla.com/tbj/i486/?version=3.2.0.12

[TheKit]

devel-su zypper in droid-compact-v820w-droid-system

And everything is working again :)

Should be devel-su zypper in droid-compat-v820w-droid-system (see http://repo.merproject.org/obs/home:/TheKit:/compat-v820w/sailfish_latest_i486/i486/)