tc-gd
commented
6 years ago It seems to be to this known issue: https://gitlab.com/fdroid/fdroiddata/issues/979
Open tc-gd opened 6 years ago
tc-gd
commented
6 years ago It seems to be to this known issue: https://gitlab.com/fdroid/fdroiddata/issues/979
tc-gd
commented
6 years ago this could be required fix: https://git.replicant.us/replicant/frameworks_base/commit/?id=953d2a3493aaceb3209afc7eef1ff1e7f7242908
MagnusAlm
commented
6 years ago Thanks for pointing to this fix/workaround, I can now use Spotify with my Aquaris E4.5 and Lineage 13.0 and a couple other apps that sent my phone into a bootloop.
tc-gd
commented
6 years ago You're welcome. Problem is that I am still fighting with ROM compilation myself and build instructions are not much clear on this. Could you please help me with https://github.com/Pablito2020/android_device_bq_krillin/issues/14 in return?
Thanks in advance.
MagnusAlm
commented
6 years ago '#' Updated* (instructions taken from https://github.com/Pablito2020/pablito-scripts mm.sh and install-everything.sh the guide was there all along ;-))
'#' For building 13.0 on Ubuntu 17.10 '#' For building 14.1 replace 13.0 with 14.1 '#' Install libraries needed for compiling
sudo apt-get install -y git ccache automake lzop bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng maven
sudo apt update
sudo apt upgrade -y
sudo apt-get install -y openjdk-8-jdk
mkdir lineage13.0
cd lineage13.0
# Check if the repo tool is installed, if it isn't installed then install it.
if ! [ -f /bin/repo ]; then
mkdir ~/bin
PATH=~/bin:$PATH
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod 760 ~/bin/repo
fi
'#' if building 14.1 you must add a user name and email berfore "repo init", not needed on 13.0.
git config --global user.email "Your email @ here"
git config --global user.name "Your name here"
repo init -u git://github.com/LineageOS/android.git -b cm-13.0
repo sync --force-sync
git clone https://github.com/Pablito2020/android_device_bq_krillin.git -b cm-13.0 device/bq/krillin
git clone https://github.com/Pablito2020/android_kernel_bq_krillin.git -b cm-13.0 kernel/bq/krillin
git clone https://github.com/Pablito2020/android_vendor_bq_krillin.git -b cm-13.0 vendor/bq/krillin
git clone https://github.com/LineageOS/android_external_stlport.git -b cm-13.0 external/stlport
'#' I you need "su" on 13.0, edit "device/bq/krillin/device.mk" and add at the end:
# Superuser
WITH_SU := true
'#' The minimum change to make 14.1 build, is to remove the following line from "device/bq/krillin/Boardconfig.mk"
BOARD_WLAN_DEVICE := MediaTek
'#' Start build
. build/envsetup.sh
brunch lineage_krillin-userdebug
MagnusAlm
commented
6 years ago As for building 14.1, compile completes but after flashing it nothing happens after reboot. It won't even show the battery charging animation in off mode.
tc-gd
commented
6 years ago Thanks! This was exactly the piece of information I was missing!
sleep-walker
commented
6 years ago It got me further, but I ended soon with:
cts/tests/core/runner/Android.mk:18: *** BUILD_CTSCORE_PACKAGE must be defined. Stop.
make: Leaving directory '/Devel/krillin/custom_rom'
#### make failed to build some targets (5 seconds) ####@sleep-walker You get this error when building krillin for lineage 13 or 14.1?
sleep-walker
commented
6 years ago This was from 13 - following your guide literally.
MagnusAlm
commented
6 years ago I might have missed something essential then, I'll test it on another machine tonite.
sleep-walker
commented
6 years ago Thank you! I'll try to fix README after.
MagnusAlm
commented
6 years ago These seems to be missing from the guide I made:
I think those make it worse, I removed that ........
(I've not tested if this is the cause of Sleep-Walkers compiling problem.)
MagnusAlm
commented
6 years ago I haven't managed to reproduce Sleep-Walkers error but got some random crashes and lockups in a virtualbox machine I've setup tonite, probably because I forgot to install VBoxLinuxAdditions.run.
I'll know in the morning if that helped.
(It didn't, note to my self, don't use hard drives with faulty sectors...)
sleep-walker
commented
6 years ago Well, thanks that you have tried. I'm afraid that this is still something stupid but unrelated to system or installed build time dependencies.
$ cat .repo/local_manifests/bq_krillin.xml
<manifest>
<!-- Device -->
<!-- 13.0 -->
<project path="device/bq/krillin" name="Pablito2020/android_device_bq_krillin" remote="github" revision="cm-13.0"/>
<project path="kernel/bq/krillin" name="Pablito2020/android_kernel_bq_krillin" remote="github" revision="cm-13.0"/>
<project path="vendor/bq/krillin" name="Pablito2020/android_vendor_bq_krillin" remote="github" revision="cm-13.0"/>
<!-- 14.0
<project path="device/bq/krillin" name="Pablito2020/android_device_bq_krillin" remote="github" revision="cm-14.0"/>
<project path="kernel/bq/krillin" name="Pablito2020/android_kernel_bq_krillin" remote="github" revision="cm-14.1"/>
<project path="vendor/bq/krillin" name="Pablito2020/android_vendor_bq_krillin" remote="github" revision="cm-14.1"/>
-->
</manifest>It leads to this output.txt.
This string is present only in:
Googling doesn't help. I'll try to install Ubuntu in container to build it but I'm afraid this is something implicit I miss.
MagnusAlm
commented
6 years ago @sleep-walker From your output.txt this doesn't look like standard Ubuntu 16.04: HOST_OS_EXTRA=Linux-4.13.12-1-default-x86_64-with-glibc2.2.5
Had a second try with a fresh virtualbox installation with Ubuntu 16.04, it worked.
sleep-walker
commented
6 years ago I am preparing my Ubuntu 16.04 chroot for try right now. My distro is openSUSE Tumbleweed, I installed matching packages. The build shouldn't be distribution specific...
MagnusAlm
commented
6 years ago No it shouldn't but what libraries that works changes sometimes.
If you whan't to use a rom that I built, you can find it here:
https://drive.google.com/file/d/1tcz2pE_vM-CW5hxH5jTB0ul60_l7OYiB/view?usp=sharing
tc-gd
commented
6 years ago It seems that building in Ubuntu chroot works. I can't identify the difference to my environment. Thanks for your patience.
There was also missing rsync and maybe others but I am building.
Thanks for your build - it will be useful for others for sure but I'd like to play more.
It seems that there are still power users of this phone but noone is maintaining any ROM from security perspective or other known problems.
I'd like to add also blueborne fix (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e860d2c904d1a9f38a24eb44c9f34b8f915a6ea3), adjust speaker volume, etc.
(@tc-gd == @sleep-walker)
MagnusAlm
commented
6 years ago @sleep-walker Had any luck with building the rom?
I've made a blueborne patch for krillin kernel 13.0, it's on the google drive link a few post up, the file "bb_patch" if you'ld like to test it.
Used this as a template: https://github.com/KonstaT/android_kernel_huawei_msm8909/commit/c779e2e5095435970bdf1090b74e1d4877a3dc66
I'm building with it now, so I don't know yet if it works.
Update: It doesn't seem to break anything ;-p
sleep-walker
commented
6 years ago I finished the build of CM13 but my ROM build has problem with ADB (cannot authenticate fingerprint), cannot format SD card as internal and for some reason cannot install SuperSU for LineageOS. Besides that it is working well and seems to be faster.
MagnusAlm
commented
6 years ago Congratulations :-D
I've so far not used ADB, SuperSU or tried to use SD card as internal, but I could look into it if you could provide some more details. I have two of these phones, got the second one for testing stuff.
sleep-walker
commented
6 years ago Thanks!
I compared your ROM with mine and at least we have the same list of files - that is good start.
BTW. do you know what is status of CM14?
MagnusAlm
commented
6 years ago I've actually just a few minutes ago managed to boot a Frankenstein build, with some QnD patches to overcome the miss match of vendor 14.1 and device 14.1:
Pablito2020/android_device_bq_krillin cm-14.1 Pablito2020/android_kernel_bq_krillin cm-14.1 Pablito2020/android_vendor_bq_krillin cm-14.1
Buggy as hell tho, but you can make phone calls, send SMS, surf with wifi.
Not tested the install with gapps.
Sim data is of cource broken since vendor cm14.1 is missing bits and pieces for that with device 14.1. It reboots when you connect it to a pc with usb cable, but it pops up as a device in explorer after reboot.. No off mode battery animation, instead it boots up after charger is inserted.
Was built on a fresh Xubuntu 17.10 install with just the stuff from "pablito-scripts/install-everything.sh". The script in it self didn't work but I installed what it was supposed to install manually.
MagnusAlm
commented
6 years ago There was a patch for bootlooping apps added to cm-13.0 the twelfth of December last year.
MagnusAlm
commented
6 years ago And I think I found the cause to the "off mode charging" bug on kernel cm-14.1.
https://github.com/Pablito2020/android_kernel_bq_krillin/issues/2
tc-gd
commented
6 years ago WITH_SU fixes me both ADB access and gaining root right.
Installation of some applications from F-Droid repository exposes system bug.
Symptoms are: In installation wizard, moment after pressing 'Install' button, message appears about 'Play Store' to unexpectedly end and reboot loop starts then.
Revert: Press volume up&down at the same time to get to Safe Mode, where you can uninstall problematic applications from Settings/Applications. After reboot all works again.
Workaround: Use some other version.
Affected applications I identified so far: Telegram, Orgzly
crash:
tombstone_04.txt