Search results

Well of course, if you don't do step 2 (flash the regular TWRP installer zip like a Magisk module.) then you will lose twrp. Was it intentional to leave it out in the quote? When you do all 4 steps you will end up with a updated OxygenOS in the active slot and TWRP and Magisk in both slots. But...

The easiest way to upgrade a rooted Oneplus 7 Pro was posted by Adam Conway on the XDA Portal. Only 4 steps are needed. I have updated my Oneplus 7 Pro 3 times this way, without any issues whatsoever: install the OTA as usual (don’t reboot) flash the regular TWRP installer zip like a Magisk...

The first official LOS16 nightly was broken (bootloop), but the second one was OK. And 15.1 is done, there won't be any more builds.

I know it's a bit hard to follow this thread with all the unnecessary noise, but a solution for Snap not working has been posted a while back. Reason: You dirty flashed from 14.1 to 15.1 to 16. 15.1 -> 16 is officially supported, and shouldn't cause any problems. Flashing from 14.1 to 16 isn't...

Oneplus3 isn't on the weekly list: https://raw.githubusercontent.com/LineageOS/hudson/e05e45c35d5e12f74788b694fcf601b8f3c6a250/lineage-build-targets

Haven't found any issues either. Battery life and performance are the same. And I haven't had any crashes of apps or system. Except for Snap not working because I dirty flashed from 14.1->15.1->16. But somebody posted a fix for that in the LOS 16 thread.

Yes,after a clean install of LOS, my phone had the same issues. But the jitteryness completely disappeared after a couple days. It's possible that some kind of background optimization (eg. TRIM) solved the issues. But that's just a guess. I changed to F2FS, and it seems like you can't manually...

My phone is making clicking noises and has dropouts when playing music over bluetooth. Rebooting helps, but I don't want to reboot everytime I'm listening to music. Does anybody else have the same problem? I think it was always like this on LOS.

Works fine for me.

I feel the same way about this. Especially because OTA updates aren't possible on this official port because you need to flash firmware first. At least an official firmware update zip would be nice.

After flashing the latest firmware i thought GPS is working again. But today my phone again lost its lock a couple of times on my way to work. Does anybody know a solution to the GPS issues? Is this maybe only happening when dirty flashing LineageOS over CM? I also noticed that on CM there was...

I had the same issues, but today I flashed the latest firmware from OOS 4.0.2 and GPS seems to be working fine now. I only tested it for a couple of minutes. But I got a fix on 18 satellites (GPS, Glonass and Beidou). Before flashing the firmware I rarely got more than 10 satellites and my phone...

LineageOS Changelog from the Play Store: https://play.google.com/store/apps/details?id=com.vasudevrb.cmchangelog

I'm using the official nightly, and notification LED is working.

I upgraded my Nexus 4 from Cm13 to lineage14.1 and flashed opengapps pico, just like you did, and everything is working fine. On my Oneplus 3 I have already been on CM14.1.

So the experimental build was working, but the nightly wasn't? Thats weird... You have booted the experimental build before flashing the nightly, right?

I don't know about SuperSU (had issues with it in the past, and never used it again). CM/LAOS nightlys have always been very buggy but I can't remember having any issues with the built-in su a single time. And I'm using CM since CM8 ;)

cm14.1 and OOS4.0 both support f2fs and ext4. No need to change anything (but f2fs is faster).

I'm using twrp-3.0.2-1.28-oneplus3.img. twrp-3.0.2-0_blu_spark_v11-op3.img is probably a newer version.

The one by blu_spark seems to be the only working one. https://forum.xda-developers.com/devdb/project/?id=15934#downloads Official and unofficial by dianlujitao don't work at all, and that modified twrp version everybody seems to be posting when somebody is asking, is very buggy. (Can't mount...

There's a button to toggle data on the top of that data usage page.

I didn't mean to offend anybody... My issue is that you don't tell us which nightly this mod is based on. I'm sorry if I haven't been clear enough. Once we get a new stable release, you could just make a zip based on it, and this wouldn't be an issue anymore. Flashing cm13 nightlys is pretty...

If I understand this right you are simply replacing framework.jar and services.jar with this flashable zip. This seems like a really bad idea. You didn't tell us which nightly your files are based on, so there will probably always be a version mismatch. (todays nightly with framework.jar from a...

Not possible as the sensor used in the Oneplus 3 (Sony IMX 298) doesn't support it.

Next cyanogenmod nightly will have dash charge. Steve Kondik himself was working on it. I guess now it's time to install cyanogenmod on my Oneplus 3 :)

When I got my Nexus 4 I immediately flashed Cyanogenmod 10.1. Until Cyanogenmod 13 I never wiped data. I only flashed the bootloader and radio from the latest factory image, and the latest release of twrp. After that I made a twrp backup (I never needed it, but having backup is always nice)...

Generally the cm13 nightlys are stable, but there are occasional issues you have to expect. Bluetooth LE was broken for a while, then the Quicksettings disappeared, after that one nightly didn't boot at all. Todays nightly seems to have some issues with 3G. Those are just regressions, so they...

It has been built for all devices now, and is available to download. Sadly the build for many devices including the Nexus 4 failed.

Other devices have issues with BLE too, so it's not the change I mentioned.

Same with my Mi Band. cm-13.0-20160109-NIGHTLY-mako is the last one with working Bluetooth. It could be some issue with Bluetooth LE, I can still connect to my Laptop or Tablet and send files. This change probably broke Bluetooth. If I haven't missed anything that was the only change affecting...

Seems like there's no face unlock on the Nexus 7 anymore. I wanted to try out the new Lollipop face unlock but the option is gone...

Of course it has immersive mode, but what you are searching for is a cyanogenmod feature. On stock android only apps can start immersive/full screen mode.

I tried it too a while ago, but i couldn't restore my data partition. How did you copy the data back? With aroma file manager?

.98 for M7 (android 4.4.2) .02 for nightly (android 4.4.3) I'm using .02 with M7 and it's working fine for me, but it could cause problems. Btw. bootloader updates aren't necessary. Cyanogenmod developers are saying you should stick to the stock bootloader. I'm updating it anyway, just...

20140606 gapps are working fine with M7.

I think since CM10.

Dialer isn't opening correctly on the Nexus 4 either. It's a CM bug. Pretty annoying anyway... https://jira.cyanogenmod.org/browse/CYAN-2949

You can use cyandelta, it's working perfectly well. I think they said they will include delta updates in the future but I guess it's not a priority because we already have cyandelta.

Build failed, no nightly today.

Servus ;) National roaming on 3AT is working since M1. Only the setting to switch national roaming off is gone. I don't know why you should switch it off anyway.

On CM it's called expanded desktop. If it's enabled in the settings you can switch from normal to immersive mode in the power menu.

Whats happening at cyanogenmod right now? Since midnight they merged more than 50 commits. I don't think it's wise to make as many changes at once. Normally I test fixes/new features, but I won't test 50 changes at once...

I thought there are no touchscreen issues when using init.d scripts, but after a day or so, the touchscreen stopped working again... With s2w/dt2w disabled everything is OK. But I have only tested it the last 2 days.

I don't know about /data/local/ but the files in init.d don't have the sh extension (for example: "99user"). And have you set the permissions to executable? I have been using init.d scripts on cm for a long time now, and it has always been working.

I made some flashable zips for sweep2wake & doubletap2wake + Battery life Extender (97%). This should work on all ROMs with init.d support. addon.d script for cyanogenmod is also included. (no need to flash it again after rom update) With the reset.zip you can delete the scripts.

I thought the touchscreen stopped working because of s4w, but I have disabled it now and it's still happening. For now I'm back to cm stock. I hope it will be fixed. The battery life was impressive.

Touchscreen stops working after some time when using sweep2wake. Anybody else? I'm using cm11 with this kernel.

If you don't update your rom daily, you should stick to M releases anyway. Tap to sleep is working with PIN lock too. I'm not using profiles though.

It's working for me with pattern unlock. (M2 build)

I had the same problem. When I noticed it I downgraded to M1 but the download speed was still very bad (it was OK when I upgraded from CM10.2) In the latest nightlys it's OK again for me. Very strange...