Hot answers tagged

3

As I've found in this bug report, you can watch the current open files by running this command in a second shell: while true; do lsof | grep /data; sleep 0.2; done This checks every 0.2s which files are still in use on /data. In my case it was chainfire's SuperSU, which had a logfile opened. Additionally, I've found out that a 2nd SDCard partition was ...


3

The issue is the current build of gapps - quick workaround is to manually set the Phone/Dialer app as the default Phone App in Settings -> Apps -> -> Default Apps -> Phone App. Source: https://forum.cyanogenmod.org/topic/124381-dialer-crashes/?do=findComment&comment=590388


2

No! CyanogenMod will wipe the DATA partition, all the CACHE partition and the SYSTEM partition while installing. It will not affect anything about lock/unlock of sim card.


2

Will installing the CWM Recovery in fastboot mode break my CM13? No, why would it? But before flashing your custom recovery make sure to disable the setting Update Cyanogen recovery or Update CM recovery or a similar setting under developer-options. Afterwards, flash your custom recovery the way you want. If that doesn't work, flash a custom kernel ...


2

As it's obviously the stock recovery you've used to flash CM, that won't work as it will do a signature check and thus reject the ZIP as being invalid. So here's what you do instead: put cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip onto your device's SD card boot into bootloader now boot (not install) TWRP: fastboot boot twrp-3.0.2-0-falcon.img TWRP ...


1

As of today (May 30, 2016), the F2FS file system doesn't support shrinking. If it does by the time someone reads this, just let me know in the comments. The solution is then to delete and re-create the entire filesystem for /data. From this related answer on Unix & Linux Stack Exchange: mkfs.f2fs /dev/block/mmcblk0p36 11583168 This will do the trick. ...


1

You most probably need GApps for it to work properly. https://wiki.cyanogenmod.org/w/Google_Apps


1

adb shell getprop ro.product.cpu.abi gives you the hardware answer (e.g. "arm64-v8a" for my Wileyfox Swift). adb shell uname -m tells you what the kernel is running (e.g. "aarch64" for the same device) If you do not have ADB setup (and don't plan to), you can run the same commands in a terminal app. Just skip the preceding adb shell then: $ getprop ...


1

Step 1: Make the certs compatible (if they are not already) At the very beginning we need to figure the file name of our the cert file. The name of the cert file is a hash one can obtain from the certificate itself. For this, one needs the openssl tools. On Unix/Linux the steps are then as follows: # Obtain the hash – in my case that returned d6a2705a – so ...


1

Update: This works from Recovery mode: - Full factory reset and then: - Apply Update -> From ADB .\adb sideload cm-13.0-20160510-NIGHTLY-mako.zip


1

Go to settings menu, about phone, down to build number, tap 7-8 times. Go back to developer options in the settings menu and down until you see device usb configuration and select mtp then you should be able to transfer between the devices.


1

In my case, I needed a cross-platform solution since I use Linux. Here's what worked for me: Back everything up. This will wipe everything on the phone, including the internal SD card. Download: A PIT file you want to flash. I used this one, which resizes /system from 512 MB to 1 GB and /data from 2 GB to 6 GB Any compatible recovery. I used this one ...


1

Once nobody was able to help me, I decided to share the answer I got by myself. I was bored and had nothing to do so I started going here and there trhough the conf. menu and I found out an option to solve it. It's under Developer options. There's an option enabled called Block touch gesture events or something like this. You should just disable it then ...


1

The obvious solution to having no operating system is to add one. That's why what you can do, is to re-flash the custom ROM you are having, or a different one (maybe even a stock ROM). You can go on their page, and find your build there. Once you download the ZIP, you put it on your SD, through the computer, and flash the ZIP from there, or you can use ADB ...


1

I've spend all day with the issue of the never ending encryption (LG Nexus 5, Cyanogenmod 13) and somehow figured out to check the logs and eventually came across this question here on Stack Exchange. @mattelacchiatos hint is a good one, but a little bit complicated. TL;DR I was able to fix this by simply booting into safe mode. For the record, this is the ...



Only top voted, non community-wiki answers of a minimum length are eligible