New answers tagged

1

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


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 ...


0

The device model is hard-wired into the recovery image. Make sure that you have flashed the right recovery image for your device. E.g. TWRP lists the recovery images for both N5100 and N5110 on the same page. If you accidentally flash the wrong image, the device will still boot in TWRP recovery (the hardware differences are minimal). However, you will have ...


0

I've tested the following solution successfully on Nexus 6 running CM13 (a snapshot build) with volume rockers as HW key X and Y. If you don't want to use an Xposed module such as Xposed Additions, then I suggest you setup AutoInput (free trial) and Tasker (free trial; user guide). You must have the accessibility service of AutoInput enabled and root ...


0

Disabling the affected app in settings and then enabling them brought back the original icon: Go to Settings › Apps Select the "All" tab Scroll to the app showing up with the wrong icon on your homescreen/drawer Tap its name to open the app-info Tap the "Disable" button, which then changes to "Enable" Tap "Enable" again Done. Disabling the app cleared ...


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

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 ...


0

Link to the xda page for this version http://forum.xda-developers.com/xperia-sp/orig-development/6-0-cyanogenmod-13-0-t3238355


0

Issues like this this are often corrected by returning to a "known good configuration" before processing additional changes. I would suggest returning to the current official Google firmware via fastboot, then verify the device is booting and operating properly, then you can flash custom recovery and install a third party ROM such as CyanogenMod. ...


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 ...


0

One way of diagnosing the offending CPU hog application is to open your application manager while your CPU Usage bars are overlayed. One by one open each potential suspect (Start with your list of downloaded apps from the app store) and select 'Force Stop' while watching the CPU usage bar. If you get a significant drop then you have found the (or one of ...


0

FireChat seems to be the culprit. Changing it's permission via Settings > Privacy (removing 'Bluetooth Change allowed' solved the issue. Thank you @Firelord for pointing out at the right thread.


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 ...


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


0

Please note that first boot always takes around 5 to 10 minutes to be sure that you've got boot loop on your device. Before we go into the detailed instructions? Have you tried wiping dalvik cache? If not do it otherwise follow the steps below. Here is how I would fix this issue: Make sure that you've already installed USB drivers on the PC. Also setup ...


2

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


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 ...


0

Late response: You won't even need the official Pebble app for that. I successfully initialized my Pebble Time Steel using the FOSS Gadgetbridge app1 (CM11 here). This way you won't even need to create an account. Only drawback of this solution: access to the Pebble app store isn't implemented in the app (at least currently not). But if you downloaded ...


0

I found out more stable ROM. It was not the official one which has noise artifacts, for instance. I found some patches made by Temasek/arter97 here at points (8) and (9). Using them solves the artifact noise problem, which occurs in the official CM13 and kyasu's ROM. I also switched to Temasek ROM which seems to be one of the most used unofficial ROMs. It ...


0

Had the same poblem after updating from CM12 to CM13. Here is how I was able to fix it: I removed these two directories /data/user/0/com.android.providers.telephony /data/data/com.android.phone/ completly from my phone (Nexus 5). I used ES Explorer to do so, I had to turn on Root Mode and Show Hidden Files to be able to delete files in that directory. ...


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

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

click 5 times SETTINGS>ABOUT PHONE>MODEL NUBMER and then in DEVELOPER OPTIONS, choose USB SETTINGS> CHARGING|MTP. SOURCE: http://en.code-bude.net/2013/03/05/how-to-activate-usb-mass-storage-and-developer-options-on-cyanogenmod-10-1/


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.


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 ...


0

I had the same problem after the cm13 on my OPO a few days ago, but the problem seems to be fixed after I did the following today: Go to settings -> Apps -> Trebuchet, click on "FORCE STOP", then go to "storage" to clean data and cache. Reboot the phone. The home page may look different than before, but you can customize it again. Hope this helps solve ...


0

I have faced the same issues too and your best bet is to reset the phone via a custom recovery(assuming you have one installed) since you flashed cm13.


0

Yes!,Gapps are supported in Canyogenmod. They are supported but you have to flash them instead of regularly installing them. You can find your flashible zip easily just google it.


0

I had the same issue with my custom Virgin Mobile XT1548 MotoG3 (Osprey). Thing is, CM is more geared for phones that are CDMA. It'll break your SIM card every time you flash if you aren't CDMA. Thankfully, I still have data, but no voice. So I use a VoIP number to make my calls


0

On a custom Os like Cyanogenmod you must flash the googleapps.zip from the recovery. The apps and services aren't built in but are very easy to flash.


0

Factory Restart was the only solution.


2

It must be a problem with the ROM if it is not showing the app disabled through Settings app like this: (Click image to enlarge) Anyhow, if the Settings app doesn't show it then I see no way to solve this problem without root. If the following steps do not work then your ROM is faulty because they worked for CM13-snapshot in my Nexus 6. In case you do ...


0

This is all made with trial and error and some script copying, I have only vague knowledge of bash and absolutely no idea what I'm risking. All is done with backups and careful reflashes. #!/sbin/sh # # /system/addon.d/77-MyApps.sh # # During a dirty flash, this script will backup files and apps at /system/* # /system is formatted and reinstalled, then the ...


1

Just do 'Factory Reset'. Well, this depends upon the recovery you're using. If you're using TWRP (assuming you've v2.8.4.x or above), choosing Factory Reset would remove everything under /data (excluding /data/media which serves as emulated storage available through /sdcard as internal SD card), would wipe cache partition, and since davik cache gets ...


0

I do not know how to reproduce this problem. It simply solved itself after changing the Cyanogen themes a few times.



Top 50 recent answers are included