<rant>

I saw this post and immediately bought a used LG G6. Unfortunately it was the LS993 model which can't fastboot. So was totally excited to install and test your port, @Guf ... but won't be able to.

</end of rant>

@Lakotaubp can we not mention the telegram group if it is not open for anyone to join?

@doniks I tried joining, but got kicked out)

@AppLee said:

Before I could last at most 8h now it's up to 36 hours.
Recently I had some battery leak, but nothing a reboot wouldn't solve or simply waiting.

Wut?! What configuration options do you have? I've tweaked my governor to be conservative, but even then I last less than 10 hours. What apps are you using? As far as I can tell, dekko is my biggest power consumer...

@dobey thanks!

@dobey

libertine-container-manager exec -i xenial -c " /bin/bash" 

but apparently, while vim was removed, vim-runtime and vim-common were stragglers...

When I removed those, it finally disappeared!

Anyhow, the question still remains... how does drawer pull from the list of installed packages within libertine? would you have any code pointers for me to look at?

@Lakotaubp Does not show in tweak tool. I really don't want to reinstall (this is my daily driver), so any hints on where to look (including code) and I'll try to resolve it the hard way...

@dobey yep. icon is there. does not start (screen blinks, then goes back to home). Yes, it has the actual vim logo. If you want to reproduce you'd have to go back one OTA, install libertine + vim, then upgrade via release channel. Lol.

Any ideas?

@dobey ok... so what can I do? how do I force the drawer to recognize that vim is no longer installed?

Hey, this might be related to my recent post...

How do I delete an (already deleted) app that is listed on my drawer from libertine, but that refuses to disappear? Can I just manually update/mess with

.local/share/unity-scopes/unconfined/livertine-scope.ubuntu_libertine-scope/.surfacing_cache

?

Thanks @kugiigi but the refresh didn't work, and vim isn't on any of the applications listed on that folder. I did find a reference in

.local/share/unity-scopes/unconfined/livertine-scope.ubuntu_libertine-scope/.surfacing_cache

I guess I'll play around with manually updating that file...

So, I installed vim in my libertine container (long story) but then eventually removed it. However, it is now still on my drawer. Where do I need to update to let it know it is out of sync?

@dobey got it, thanks!

Mobile UI isn't an easy problem to solve, which is why you're seeing some many - often conflicting - positions and requests. I have only been involved since the covid outbreak, and was able to daily-drive both options. My preference: the drawer. That said, there are positives from the other option as well.

I do believe, however, that my mobile phone shouldn't necessarily have the same interface and interaction as my desktop.

@dobey Super curious here.. the lack of support for CDMA is because of what, exactly?

know what? a little birdie just reminded me of this page: http://docs.ubports.com/en/latest/porting/ubp-5.1.html

it kinda says everything that needs to be said, no? had you seen this page? did you have to do something else? actually, which device are you working on?

I'm thinking of moving that page from porting (where frankly I had overlooked it) to system software development section....

I agree

about newer compiler ... I am pretty sure that the actual compiler used is some old precompiled (forked?) gcc that has been stuck as a binary inside the android repo. And I am also very sure that noone wants to (should) invest time to officially transition to a newer compiler. That would be way too much effort wasted on old android forks.

Yeah, I think I took a curve on the instructions, since I do not recall using any precompiled compiler.

I'm on:

gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0

arm-linux-gnueabihf-cpp (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0

arm-linux-androidebi-gcc (GCC) 4.8

and I definitely had to update a bunch of files to get it to build. That said, I do use my Nexus 5 as a daily driver, and I don't think we have anything as feature-complete using newer code, is there?

@rival Have you checked if your user can run docker? That is, docker ps works? I think I hit a similar issue that was resolved when I added my user to the docker group

@doniks Can do! However, I did all of this on my Linux Mint 19.1 box, so there were some required code changes in order to build everything. I am still working my way through the folders to match code-to-repo (since repo sync isn't your typical gitsubmodules (!)).

In the porting page, there is an explicit call out that ubp-5.1 ports must be built using Ubuntu 16.04. A container or virtual machine based on 16.04 is recommended for this purpose. So I'm unsure who to touch base with to see if guidance can officially transition to a newer compiler (including changes on all the respective repos). Would you have a name? Feel free to PM me.

So a follow up to this, for others...

After completing all the steps in https://github.com/ubports/device-builds, I then did the steps in https://docs.ubports.com/en/latest/porting/ubp-5.1.html

That is, reboot into fastboot and

fastboot flash boot boot.img
fastboot flash recovery recovery.img

Reboot to validate new kernel

uname -a
lsb_release -a
cat /proc/version

Then fastboot again and do

./replace-android-system system.img

From https://github.com/janimo/phablet-porting-scripts/blob/68734ca07998b8e784397df77d9aca4b968b3815/build/replace-android-system

In my Nexus5, I had to modify the script since I fastboot'ed already...

read -t 10 -n 1 -p "Reboot to recovery (y/n)? " answer
[ -z "$answer" ] && answer="Yes"  # if 'yes' have to be default choice
case ${answer:0:1} in
    y|Y )
        adb reboot recovery;
        wait_for_device;
    ;;
    * )
        echo "Assuming device in recovery mode";
    ;;
esac

Once you reboot into UT, you can validate the updated build properties...

cat /android/system/build.prop

which should match what you built on your machine!