@phoenixlandpirat Thanks for the information. But old phones are not so easy to find. and then many of these have prices that are exaggerated. If you think about it, it's better not to buy another phone just for another operating system. I personally bought my phone a few months ago and it seems stupid to change it just because it mounts Android and not Ubuntu Touch. I just hope that those who are now working on porting ubuntu touch have understood that we need to change the situation, and if we do not do it now, we risk losing hope to many people, who like me believe in this operating system.
@thekit That looks amazing!
I'm guessing that incoming calls is the biggest questionmark in my head.
But I have to say very well done!
I know it's an early question but is it possible to run Android apps via Anbox?
Is it possible to dualboot?
Remember 16.04 will be supported in 3 more years.
Would I be able to install a 18.04 desktop container?
Once more, I love the work you have done!
@flohack said in Porting Halium to Nexus 7 deb:
@doniks maybe @UniSuperBox can comment a bit on the manual tweaks you had to do for rootstocking the device, actually all should come out of the box somehow.
Well, in a way he did :) The PR for the update of docs.ubports is in, which means both ubports-boot and rootstock-install can take their bugs with them to the grave.
Then, if plasma mobile shows a screen, we should be able to do this, too right?
One would hope so. However, even with halium-boot (and a bunch more kernel configs it wanted) I managed just now to build and boot it, but I end up with the same segfaults :(
I spoke to @UniSuperBox and @bshah earlier today on telegram. There was a theory about something with libhybris and "N linker" but I didn't really get it and atm still just google logo.
You cannot install Ubuntu Touch on a device that it has not been ported to. That's why the installer will not recognize your device.
If you would like to port Ubuntu Touch to your device (porting is not the same as installing), please see the documentation.
@doniks I booted the phone, left it alone for roughly 15 minutes then connected and got the outputs for you, I tried lxc-android-config instead of systemctl and got a "command not found" error. heres the outputs for you:
let me know what you think I might be doing wrong or missing.
I noticed the output of find this time is much smaller than what I got last time, but again, I connected to the phone (it reset connection a couple times which is the errors at the top of the log output) and ran the commands you asked me too and copy and pasted
@r-h3r0 kernel doesn't seem to compile.
e.g., error: 'mipi_samsung_disp_get_power' undeclared here
Maybe best if you build lineageos first. Just as a stepping stone to make sure everything is in place for you to build the kernel. No config changes, no changes at all, just build as los describes.
I guess the alternative would be to poke around in the code and try to figure out why it doesn't compile.
(For reference, I take it this is your porting issue, which shows your manifest : https://github.com/Halium/projectmanagement/issues/59 )
Another small practical tip that helped me with pinning down build errors: do make -j 1 instead of mka because then it just builds one thing at a time, which might help with tackling the build failures one by one.
@flohack said in Samsung porting notes, a loose collection:
Instead, the device needs to be brought into "Download Mode". This can be achieved by:
Manually by pressing Vol-Down, Home and Power button until the green warning text appears
On my Samsung Galaxy S8, there is no physical home button, only virtual on the display.
I figured out, instead of the Home-Button, I need to press the Bixby button, below Vol-Down,
then the green warning text appears...
@bastos No sorry, this will not help Bluetooth problems on the user/app end. This is driver updates for making a Bluetooth device visible at all. So all our kernels already have to have this patch inside :)
I was hoping to get more issues resolved with xenial but it seems that Bluetooth in 15.04 is already a backport of 16.04 - So we will see but unfortunately it can be that we will carry on those connection problems and crashes :(
Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.