Hi @rocket2nfinity
I guess that makes it 2 who used it as a daily driver 🙂
I suspects that @Flohack have to many devices to maintaine, maybe it gets ported one day when he has nothing else to do 🙂
Couldn't we have som download statistics on the device page? Showing how many downloads each ported device have since they was added to the ubports installer. I know this wouldn't be fair for those devices that hasn't made it to the installer yet. But none the less it would be interesting to see some numbers showing how active this project is. 🙂

@tabasco Check here for details https://devices.ubuntu-touch.io/device/angler/

@flohack
I rebooted the phone and the bluetooth didn't work. I rebooted again and the bluetooth was working again. It is a little flunky if it woks or not. I have a bluetooth keyboard it was a long time since it worked with my phone. I tried to connect to the keyboard just now and the phone hard crashed, it rebooted, no changes there ☺

@eirikr1848
Hi, I think the way to do such thing is to gather everything required on your computer, build and compile it for your device target.
Then you can install the built libraries on your device (it might fit)
Or you can package it in a click for a dedicated app to use.

Note every Ubuntu Touch devices are "stuck" in 16.04 until 20.04 is available for our OS.

Explanation:
The rootfs is locked in RO because the partition size vary and is relatively small for the system image.
You can access the userdata partition to install rather large click files, but you need to build and package an app prior to use it on the phone.
You can also use Libertine container to install/use so-called legacy apps (command line software essentially)
So to tinker with 3D you might want to build your dependencies on your desktop computer and create a native app that can use thoses libs.

@flohack
So the best for me is... "wait and see" : sometimes, waiting is urgent !

@lgtrombetta First fix can be slow but often it speeds up, just use it a few more times, mine mostly is instant fix on my N7.

@flohack if you ever need a tester for a helium9 contact me id be happy to assist though

@arubislander thank you ill adjust the settings in a moment

@ubguy my bluetooth wont even stay on so idk , i just installed this on my n6p yesterday and as far as i can tell the only issues im having is the screen locking up time to tim,gps non functional and bluetooth. But my bluetooth when i flip the switch to turn it on it shuts right back off . Be cool to fix these little mishaps

Well the devices page is currently reflecting the port status:
c36b1a03-7918-4d0e-91c5-fe36624edeac-grafik.png

Wireless external monitor: I do not have a dongle to check that, but its probably not working Hardware video playback: Probably working in media-player-app but did not test enough formats Hotspot: Not working for unknown reasons NFC: Not tested, should work, but anyways there are no apps to use that until now WiFi: Disconnects randomly, a powersaving bug in kernel that disconnects the PCIe connection Fingerprint: is a gloabal problem in Halium 7.1, not ported back from 9.0 Bluetooth: Works in general, but sometimes at startup does not load firmware, a reboot is needed ADB access: A general problem in Halium 7.1, but not needed for daily operation 🙂

So if those are OK for you its a great device!

That would be nice to keep the default settings or what you customize it too. I currently just copy my files from my phone to my laptop

@flohack That would be great nice and phantastic ;O) !!!

Any news about the Fingerprint reader.

can it be possible to get it to work for OTA 16 ?

@indiandragon said in Installation instructions and files for 4-cores devices:

ated automatically or did you build it yourself? Steps to do that would be very useful.

Unfortunately I cannot build one device with 2 kernel images right now in our CI, also the installer does not know about such special animals 😉

I got the Universal installer to work.Had to flash the userdata.img file. I figured since I was coming from a custom ROM i might have too because i had to do it before when flashing to a Pixel Rom. I grabbed that image from the first availible stock ROM 6.0. If you get stuck flashing back to stock with the boot.img, see this thread. https://www.reddit.com/r/essential/comments/ihhedy/psa_solution_fastboot_error_couldnt_parse/
Hope this helps someone.

@lgtrombetta @Flohack I did update anbox via anbox-tool before adding any apps. And I used adb to install them, not anbox-tool. That might be the difference of why it's working for me.

@stanwood It's nice to go to the forum and read that my app is already recommended. Thank you so much 😀
I have now paused the development of this project (I am working on another project).
In the future, I plan to:

Add IPTV support. Desktop-mode support (waiting MHL adapter) And support for video subtitles

@rocket2nfinity thanks. So this is obviously another issue...