multiwirth
Senior Member
So. Is there any chance to get LOS 16 for OP3 ? Or should i change rom now ?
There is already an unoffical build, like for many other devices so the chance is quite high to get at least unoffical for it.
So. Is there any chance to get LOS 16 for OP3 ? Or should i change rom now ?
Gooood moooooorning xda!
lineage-15.1-20181023-nightly-oneplus3 is up for OTA
My question is about downloading this update... do I use my fibre optic home broadband at 150 MB/s or my phone's 4G/LTE connection at 127.65 MB/s or go down the pub and use their free Wi-Fi at 17 MB/s?
Gooood moooooorning xda!
lineage-15.1-20181023-nightly-oneplus3 is up for OTA
My question is about downloading this update... do I use my fibre optic home broadband at 150 MB/s or my phone's 4G/LTE connection at 127.65 MB/s or go down the pub and use their free Wi-Fi at 17 MB/s?
The real question is how many Pints of Fosters can you get down in those five minutes?
So, you can see, it is very important for me to carry out these updates and testing in a convivial atmosphere.
No scientific testing would be complete without a laboratory for your rigorous experiments. And no laboratory would be complete without a full array of glassware containing noxious, and potentially lethal, fluids.
No scientific testing would be complete without a laboratory for your rigorous experiments. And no laboratory would be complete without a full array of glassware containing noxious, and potentially lethal, fluids.
...and if the fluid contains methanol you have successfully passed the double blind test... *lol*
What is kernel config file filename for this device? Also what gcc version is currently used at lineageos build servers? I'm going to build TTL iptables module
./prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc -v
Using built-in specs.
COLLECT_GCC=/mnt/export/data/src/los15/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/real-aarch64-linux-android-gcc
COLLECT_LTO_WRAPPER=/mnt/export/data/src/los15/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/../libexec/gcc/aarch64-linux-android/4.9.x/lto-wrapper
Target: aarch64-linux-android
Configured with: /usr/local/google/buildbot/src/android/gcc/toolchain/build/../gcc/gcc-4.9/configure --prefix=/tmp/379ff75b5937fff979453ee943dd77c6 --target=aarch64-linux-android --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/buildbot/tmp/build/toolchain/temp-install --with-mpfr=/buildbot/tmp/build/toolchain/temp-install --with-mpc=/buildbot/tmp/build/toolchain/temp-install --with-cloog=/buildbot/tmp/build/toolchain/temp-install --with-isl=/buildbot/tmp/build/toolchain/temp-install --with-ppl=/buildbot/tmp/build/toolchain/temp-install --disable-ppl-version-check --disable-cloog-version-check --disable-isl-version-check --enable-cloog-backend=isl --with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm' --disable-libssp --enable-threads --disable-nls --disable-libmudflap --disable-libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions --disable-shared --disable-tls --disable-libitm --enable-bionic-libs --enable-libatomic-ifuncs=no --enable-initfini-array --disable-nls --prefix=/tmp/379ff75b5937fff979453ee943dd77c6 --with-sysroot=/tmp/379ff75b5937fff979453ee943dd77c6/sysroot --with-binutils-version=2.25 --with-mpfr-version=3.1.1 --with-mpc-version=1.0.1 --with-gmp-version=5.0.5 --with-gcc-version=4.9 --with-gdb-version=none --with-gxx-include-dir=/tmp/379ff75b5937fff979453ee943dd77c6/include/c++/4.9.x --with-bugurl=http://source.android.com/source/report-bugs.html --enable-languages=c,c++ --disable-bootstrap --enable-plugins --enable-libgomp --enable-gnu-indirect-function --disable-libsanitizer --enable-gold --enable-ld=default --enable-threads --enable-eh-frame-hdr-for-static --enable-fix-cortex-a53-835769 --enable-graphite=yes --with-isl-version=0.11.1 --with-cloog-version=0.18.0 --program-transform-name='s&^&aarch64-linux-android-&' --enable-gold
Thread model: posix
gcc version 4.9.x 20150123 (prerelease) (GCC)
Hi guys, I'm coming from RR rom and I've a lot of problems with android auto... I've read somewhere that it maybe works with lineage but RR is based on lineage too so before flashing this I wanna ask directly... Did some of you tried AA and it works totally fine? For me after random time (may be 10 or 30 mins)it freeze and I've to unplug it and use it from the phone cos it doesn't reconnect to the car anymore for at least 15 mins... Thanks guys
Have you disabled Battery Optimisation for the app? It's being killed in the window of time that is suspiciously like Doze doing it's thing.
Hm no, never...I've disabled it now, let's see if it change something...thanks mate, even if I think it's some deep problem than just doze :/
Hi guys, I'm coming from RR rom and I've a lot of problems with android auto... I've read somewhere that it maybe works with lineage but RR is based on lineage too so before flashing this I wanna ask directly... Did some of you tried AA and it works totally fine? For me after random time (may be 10 or 30 mins)it freeze and I've to unplug it and use it from the phone cos it doesn't reconnect to the car anymore for at least 15 mins... Thanks guys
That's my feeling too..no nover, I've just dl catlog app now, I'll try next time i will use Android auto and see if i can understand something, even read it lolIt might be something the App relies upon, rather than the app itself being killed. Android is so aggressive now at trying to limit background activity that it's becoming useless as an app platform. If apps can't run, what's the point?
A logcat would probably uncover the cause of the problem. Have you taken one before?
That's my feeling too..no nover, I've just dl catlog app now, I'll try next time i will use Android auto and see if i can understand something, even read it lol
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Is it possible for Project Treble to be implemented? I was thinking of using the extra space from /bt_firmware (1GB) for /vendor. Thanks.
Sent from my OnePlus 3T using XDA Labs
Oneplus already said they wont suport treble for oneplus 3 https://forums.oneplus.net/threads/join-our-oneplus-5t-ama-now.686679/page-9#post-17146313
so why not develop 3rd party suport for treble?