Or maybe not. You might want to do telnet debugging with the break=bottom kernel cmdline parameter.

@suoko it would be better you join @Halium group on Telegram. We dont want to overload the forum. And copy all such things into a pastebin plz...
Your log is very short. nothing that could help us. Please try to build Lineage with this manifest to verify if the kernel is at all working.

Attachments should work again!

@suoko Did you start using the reference rootfs?

let it bootloop once, go into recovery, look for cat /proc/last_kmsg - that will give you kernel dmesg

I am just saying that there will be no naming discussion in the near future. There are no plans to change the name, as our marketing guys decided.

BR Florian

@suoko said in Need help in porting Halium/Ubports to Galaxy S4 jfltexx:

hardware/samsung/AdvancedDisplay/Android.mk:34: frameworks/base/packages/SettingsLib/common.mk: No such file or directory

This seems to be a Java application, try to get rid of AdvancedDisplay fully.

@UmaGellan your initial post sounds like a business plan.

We are a community and not a company, so many of those strategic decisions will never be made in this way or by the time when they are necessary. Its also not what Torvalds did with Linux - he just put it there. He had no idea what it will become, and today its used by millions of devices worldwide (take Android and its for sure close to billions xD)

We can steer roughly the course where the project might go, but we do not have the budget to campain for it. And we do not want to bind us to a few but potential sponsors, as they might become too influencial over time.

Any business that thinks there is value in modding UT to a proper shape can do so, its open source. We will make slow but steady improvements, but we are not in the position to attack any corporate market, be it even a niche.

If you get the wrong redirect, just press on the UBports Forum logo and you are in

BR

Well problem is still with image uploads... unfortunately

No image data is passed through that part of the container, so you are not at risk using UT. Idk why this dependency is in, but probably it could be removed from the lxc container.
BR