Search results

Today's build succeeded. The new image is much smaller (390MB for the Aug. 27 build vs. 412MB for the Aug. 6 build). I therefore was able to install it together with Open GApps nano (instead of pico) package and it seems to run fine.

And it failed again: https://buildkite.com/lineageos/android/builds/25852 Worse: also all builds for other devices seem to fail in a similar way: https://buildkite.com/lineageos/android/builds/

Same here. I dirty flashed the August 6 build of LineageOS 17.1 + Open GApps pico over my existing LineageOS 16 install and it works fine. Important: the Open GApps nano package is too large and does not fit on the system partition. With the pico package, it works fine.

Great, I hope this set of changes will be accepted soon!

Yes -- it is related to the Flip Cover settings. Have a look here: https://forum.xda-developers.com/galaxy-s5/development/rom-lineage-os-samsung-galaxy-s5-lte-t3534283/post71605146#post71605146...

I forgot to mention that I already did that. I did a factory reset and tried to connect to my WiFi network in the setup wizard. But no networks are shown there. So it seems to be hardware related - either a broken or maybe a wrongly configured/programmed chipset. Anyhow, I now ordered an S7 so...

My Wifi and Bluetooth all of a sudden stopped working and I can't re-enable them. I see the following in logcat: D/WifiHW: finit_module for "/system/lib/modules/wlan.ko" failed: No such device E/WifiStateMachine: Failed to load driver Anyone seen this? I'm afraid it might be a hardware...

I'm using it as a daily driver for a long time already and it's pretty stable and it performs well. It has much more RAM available than the stock ROM as it doesn't include Touchwiz and Samsung's many preinstalled apps. Battery life is good. Camera is sometimes a bit unstable, but it overall...

Download and install the package "addonsu-arm-signed.zip" (you can find it here). More info on the reason to exclude root access from the default images can be found in this thread. In a nutshell: adding the option to root the phone breaks apps like Pokemon Go and Android Pay. Also, Google's...

I can confirm that the phone crashes when visiting typefrom.com (using Chrome).

Why do you even use this ROM if you think it's all bad?! No, this isn't a Samsung ROM. Instead, it's much closer to vanilla Android, but with many neat features on top. There is an (often better) alternative for nearly every feature in a stock Samsung ROM. And it's also much faster and better...

Do you have any clue what's going on here, cvxda? Anything I could/should test?

One of my apps (this one) has problems accessing the camera. I captured the warnings and error messages (using 'adb logcat *:w') and the log shows that the camera daemon (/system/bin/mm-qcamera-daemon) even crashes. Not sure what's going on... but I attached the log file for analysis. (I'm...

There's a new build available: https://download.lineageos.org/kccat6

That's a known (minor) issue. And not related to the boot loader (but probably the kernel, or Lineage OS).

Works flawlessly, thanks! It may make sense to add the link/explanation for upgrading to the official weeklies to the TS / HowTo.

I tried to dirty flash this over the previous test builds, but that doesn't work ("Can't install this package on top of incompatible data. Please try another package or run a factory reset"). cvxda: I guess we would need a migration build to migrate from your builds to the signed LineageOS...

It's in settings, under 'Device'.

That's a good one, I will definitely try that! The other phone is a OnePlus One with a cover, so this S5 might detect that when I stack the two phones. I'll report back in due time (either when I experience this behavior again with Flip Cover disabled, or when I haven't experienced this issue...

What I probably should add, is that these screenshots were automatically generated while rebooting the phone by holding the Power + Home + Volume Down buttons (I'm not sure why it results in creating a screenshot, as I thought that this function would be disabled while the phone is locked).

Has anyone seen the following behavior? During the night, I often stack my phone on another one. So one phone is laying on top of the other. Sometimes, I get a weird lockscreen in the morning and cannot unlock the phone anymore. See attached images. The only way to fix it is to reboot the...

I just donated. Thanks for all the hard work! Would it make sense to add a donate button to the topic start? (I had so far overlooked the donate button in your profile).

I'm also not arguing that nothing changed. ;) Can you see the kernel versions of the two images (e.g. using logcat)? If I remember correctly, xamio switched between kernel branches around that time. This may provide a hint on where the problem is.

Note that file size doesn't say everything... Could also be that xamio switched to another compression scheme, or included an extra app or so. You could have a look at the git repositories which are linked to from the download pages (by xamio & cvxda) to get some hints.

Thanks for the new build, Corinna! This bug is now gone again: :)

xamio, cvxda: I noticed that the camera display is again distorted in apps like WhatsApp on the latest build of LinOS (Feb. 27). See attached screenshot.

Did you perform a dirty upgrade? If so, have you looked at the following note: You have to reinstall the GApps package immediately after performing a dirty upgrade, otherwise you may/will get troubles.

I'm using boot loader CQA2 and baseband CPJ1.

The phone is again fully stable since this build (Feb. 27). No more spontaneous reboots or shutdowns. :good:

Thanks, I just installed it! I will report in case I still see reboots.

xamio: could you make a Lineage OS build with the same kernel? Would probably be a good temporary solution to get to a stable ROM again.

I have the same feeling... I just had for the second time that the phone became unresponsive while scrolling through a page (in the browser) and then it shutdown. So it may somehow be related to the GPU (driver). xamio, cvxda: could it somehow be related to this patch in combination with newer...

Thanks -- and also great to see that you're trying to upstream your work (to the Lineage OS repos)! :good:

I also now and then experience a shutdown (not reboot) with the last version. This is a known issue and Corinna (@cvxda) is working hard to track down the patch to the kernel that causes this. The video issue is also a known one; and a patch is being prepared upstream (Lineage OS). So this will...

So if I understand it correctly, you can not upgrade to newer versions than Feb. 12, but you can restore a backup of version Feb. 12? Correct? So you can do a clean install of newer ROMs (> Feb. 12), boot into the OS, restore the apps (via Google) but when you then reboot, the device hangs...

Well, I indeed don't get it. The only thing that is important in order to be able to boot your OS is that the /cache partition is available and has the right format. It is not such that this partition needs to contain some specific content -- the OS will boot fine when you completely wipe the...

Indeed, the item is there (in the Feb. 20 build). I simply overlooked it. Why would you need that? You should be able to simply wipe (format) that partition from recovery and restart -- I do that all the time when updating (dirty flashing) the OS. The /cache partition does not include any...

It is listed under Settings > Apps and it's running (started on boot). The app just doesn't seem to have an interface, so you can't start/open it. I have no idea if it does anything, because I have no flip cover for my phone.

Seems like a fix was found for the video scaling issue: (Cross-post from the Resurrection Remix thread)

Just FYI: I have not seen reboots with the Lineage OS ROM (with 3.10.104 kernel) using the default governor.

You'll find out, when you look at the list of known bugs in the topic start... ;) (So yes, there's a problem with the playback of 720p videos)

Lineage OS no longer ships with root access enabled. Have a look here for the reason behind it: https://forum.xda-developers.com/lineage/general/lineage-to-ship-root-access-default-t3540423 You can still enable it, just download the right zip file here and flash it...

Could this somehow be a problem caused by wrong permissions (SELinux)? It seems like there have been similar problems with kodi running on Android. Quote from that thread: Is there an easy way to temporarily disable SELinux to see if the problem disappears?

Thanks for the hint. I planned to do so, but apparently forgot it... What happened: I had already copied the complete RR modules directory next to the original (LinOS) one (/system/lib/modules), but apparently I forgot to swap them... :rolleyes: I now swapped the two dirs and everything seems...

You're right... but I'm just somewhat surprised that there are such substantial functional differences. I was under the impression that a difference in subversion (major = 3; minor = 10; sub = 96 vs. 104) designated security and bug fixes only, as with the normal Linux kernel. Of course there...

I tried flashing the latest kernel provided by cvxda (the kernel 3.10.96 from the Feb. 10 RR build) on my phone running Lineage OS 14.1 (Feb. 02 build), but also with this kernel, WiFi doesn't work on LineageOS. See attached screenshots. Something must be different between RR and LinOS.

As you can read here and here, cvxda and xamio by mistake created the current 3.10.104 kernel from upstream (plain Linux) and they are now in the progress of updating to the latest from the Google android-3.10.y branch to get all the Android-specific patches as well. Kernel 3.10.77 is as far as...

Just wanted to say thanks for that. Even with the upstream (plain Linux) patches it already works nicely, so things can only get better. :) As an experiment, I just flashed this 3.10.77 kernel (the boot.img from the Feb. 03 RR build) onto the boot partition of my phone running Lineage OS 14.1...

Hmm, NFC peer-to-peer (Android Beam) is indeed not working. When tapping another phone, the screen locks and I see this in the logs: E/BrcmNfcJni(....): nfaConnectionCallback: unknown event ????

I just checked and I can read NFC tags without any problem with the Jan. 31 build. Is NFC enabled in settings? Or maybe the NFC stack crashed (try resetting it by disabling & re-enabling NFC, or by rebooting the phone)?