FWIW, this thread http://www.android.gs/backuprestore-imei-and-nvram-on-any-android-device/ explains a liiittle bit about nvram, so now my theory is that while the "error X 10" is a mediatek-ism, we might have related problems about this nvram not being right. That doesn't give me a solution, but, uhm, not sure what it gives me :)

Also, not sure this is related, but for years I have an expired sim card in it and the device has seen long (months) periods of flight mode and/or never powered on.

EDIT: Seems, lots of xda and similar sites talk about nvram in relation to IMEI being zero (invalid/forgotten). Mine seems to be ok (at least not zero). How about you? You can see it in settings. Do NOT post you IMEI! Seemingly this is some super secret unique identifier for your device.

Would be good to explain the liberapay situation: https://forums.ubports.com/topic/1456/liberapay-is-in-trouble-with-mangopay-but-dont-panic

@arubislander said in Could I get a step by step guide on how to install Transmission via libertine:

Again, I have no idea if transmission will work in a container, but the above steps should help you to find out.

I have used transmission in the past on UT and I can confirm it works (worked) quite nicely. Transmission also offers a web interface, so you can use it from the touch enabled browser!

@ierihon said in Need Help: WebApp for Internet Radio:

But with Radiolise i have error: "something went wrong" :(

In standard browser Radiolise work well.

sounds like user agent string. some websites behave differently when they think you are using ios/android/windows/edge/firefox/younameit in an effort to be more compatible, but sometimes they end up being more broken with less popular browsers due to their naive detection logic.

you can try different user agent strings with the webapp

@advocatux said in Need Help: WebApp for Internet Radio:

Meanwhile you fix those issues, maybe you can use https://open-store.io/app/uradio.rubenxparra

It's suuuch a pity, but rubens website with the radio database has gone away, which kinda renders the app useless :( It was working quite nicely and the database was libre licensed. A shame.

@ierihon said in Need Help: WebApp for Internet Radio:

I try to make UT WebApp with WebApp creator, but i have same troubles:

• not play radio in background;

apps do not execute in the background on UT. I think other audio apps probably pass the stream to some UT api and then UT plays it for them.

You could check how for example uRadio passes the stream to the system.

Alternatively, as a bit of a hack, you could use ubuntu touch tweak tool to allow background execution of your app.

• and, i mean, some issues with versions(i use Vivid app on Xenial): after second launch app won't work.

Hard to say without any other info. What does a good and a bad log file look like?

I think normally (but yeah "normal" only goes so far in android world) the last_kmsg should always be there provided you reboot and don't power on/off!

quick look at your config, mer checker complains about CONFIG_ANDROID_LOW_MEMORY_KILLER (and some "optional" ones, not sure the impact, but might be worth a try if you can enable them. But I've also not set all the optional ones in my port)

halium and pm - definitely check them first.

My Nexus 7 deb also doesn't remember the wifi password anymore. I have to enter it after every reboot. In the settings somewhere I can see that there are "remembered" connections accumulating, but they seem useless.

I have a vague memory that a similar issue was discussed at some point in the past, maybe it was even back in Canonical days, but I don't remember the details, let alone what if any solution there might have been. I've also never actually sat down and properly searched for it :-P

What are you referring to when you say "NVRAM ERROR X 10 or."? Is that some kind of error message you get?!

@synnyg_r ok. Lets see the kernel logs once you rebuilt. Also can you connect to halium rootfs? And pm works a bit better with halium as of now, try that also!

@synnyg_r, Port to Xiaomi mi4 - SSH connection refused

Everything went nicely as the device has correctly booted (it show "GNU/Linux Device on rndis0 10.15.19.82" through a dmesg -w, here is the result : https://pastebin.com/qTubjaQU) but I'm not able to access the device through SSH. Even if I followed the instructions at http://docs.halium.org/en/latest/porting/debug-build/logging-in.html, ssh phablet@10.15.19.82 does nothing, as a ping to it. The thing that I didn't understand is the tutorial mention the .82 ip but in my case it's still unreachable after the modification. So I tried to SSH to 10.15.19.100 (the address you have to set), and now the device is reachable BUT I get a pretty "connection refused" error.

.100 is your local build machine. .82 is the ut device

I used the latest rootfs available on UBports server, is a problem known with it ?

I think there were at some point ... not sure of latest state.

1. try redoing the ip link stuff, sometimes your local network manager gets into your way with the new network interface
2. check ssh -vvv ...
3. check kernel log from device

You DID set a password to use for ssh right?